Does anybody knows why there's an issue while running two builds at the
same time on the same build server?
I have the following error:
cp: cannot create regular file
`/tmp/tmpdir_ap/ck/up/config/launcher.11': Permission denied
PKG ERROR [package-prebuild.c/genfiles()] : Error 0 on system
(cp -d /vobs/tito/fdd/app/files/m2/launcher.11
/tmp/tmpdir_ap/ck/up/config/launcher.11)
On another build, I have the following error.
make[3]: Leaving directory
`/vobs/...............'
Failure in communication with signing server...........
failure getting the chain key file, aborting.
---
Unexpected error!
Two builds running in parallel are going to run into trouble if they both require exclusive access to a resource at the same time. On big projects, it may not be immediately evident that the two builds need access to the same resource because it could be the Makefile of a third party library which uses another third party library, etc.
For instance, this error message:
`/tmp/tmpdir_ap/ck/up/config/launcher.11': Permission denied
suggest that the build uses a temporary directory located in /tmp/ but whose name is not generated to prevent clashes. So if you have two folks running a build which uses that temporary directory, you're going to run into problems.
I don't know what is causing your network error but again if it is a matter of exclusive access (e.g. if the build process starts a server on a fixed port), then that could explain why the build fails.
The solution to this kind of conflict is to go through the build process to ensure that temporary directories are created to have unique names, ports can be assigned dynamically to avoid conflicts, etc.
Related
This is an interesting issue that I couldn't identify the cause is from Curl, or SCP or Linux/Hadoop.
Current environment has following command to push a build to Linux/Hadoop environment.
curl -k -v scp://this.is.a.fake.url.com/linux/mount/drive/to/hadoop my-build.app
After providing the correct username and password, the build pushed successfully.
However when I check content of the build, it is a file from previous release (an old version that was uploaded before). It almost feels like there is buffer mechanism either by Curl or linux/hadoop to keep old build (which must be stored somewhere)
I also found an interesting observation that if I delete existing build in Hadoop/Linux before the CURL command, the issue never occur again. So the problem is when using Curl to upload and replace existing file, make fresh upload without existing file is always successful
Just wondering anyone had the similar experience.
Well, HDFS files are read only. You don't modify files, you either append, or replace --> (create new, Delete old, rename to the same file name.) This is consistent with what you are seeing, and likely there is a lost error message in your mount tooling. (As it's not possible to modify it must be silently failing)
I am following the instructions here:
http://www.rocketboards.org/foswiki/Documentation/AlteraSoCDevelopmentBoardYoctoGettingStarted
I run this command
bitbake virtual/kernel
Everything works fine except it does not create a socfpga_cyclone5.dtb
I run this command, which should be the same
bitbake altera-image
And I get the error
ERROR: Multiple .bb files are due to be built which each provide virtual/kernel (/home/bobo/yocto/meta-altera/recipes-kernel/linux/linux-altera_3.11.bb /home/bobo/yocto/meta-altera/recipes-kernel/linux/linux-altera-dist.bb).
This usually means one provides something the other doesn't and should.
Does anyone know how to create that .dtb file or fix the second command? Up to that point I had no errors.
Ideally your .dtb file should be coming from the Altera software flow through Qsys and that is the one you should use, rather than the one that is created from the Yocto build system.
The Yocto build system will not be aware of the FPGA design and hence that .dtb won't be useful.
The error you're getting is mostly due to conflicting meta files. Sometimes a target might have multiple providers. A common example is "virtual/kernel", which is provided by each kernel recipe. Each machine often selects the best kernel provider by using a line similar to the following in the machine configuration file, which should be somewhere in
poky/meta-altera/conf/machine/your-machine.conf:
PREFERRED_PROVIDER_virtual/kernel = "linux-altera-3.11"
I installed Joomla on a website on Windows Azure. After trying to update the Joomla version or uploading a new template I get the following error
JFolder::create: Could not create directory
Warning: Failed to move file!
For me it's clear that the problem is regarding permissions, so the question is, how can it be solved?
Since the Azure architecture (basically the replication) makes you difficult to just change the permissions of the folders, and it is not possible to modify the folder permissions on a Windows server using FTP, I feel like I'm on a dead end.
It should definitely be possible. When installing a component JFolder::create is called several times.
I think that you are passing a wrong path or something to the actual call. Have you tried a simple test using the native mkdir()?
I am receiving the below error when I'm trying to build the solution file from MSBUILD.
I'm building the solution file from ClearCase integration stream .
When I do the same from a different system it works fine on the integration stream.
I have tried creating and writing the file into the N/W drive & it works fine.
But when I build it through CruiseControl it is throwing the following error.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(3041,9):
error MSB3491:
Could not write lines to file "obj\DAL.csproj.FileListAbsolute.txt".
Access to the path 'M:\yj73_SRDV3G_Proj_01_00_int\SRM_COMP\SRDV3G_Project\CRDB_V3\Application_Source\DAL\obj\DAL.csproj.FileListAbsolute.txt' is denied.
Two usual causes:
The CLEARCASE_PRIMARY_GROUP environment variable is incorrectly set and don't reference the primary or secondary group of the Vob \SRM_COMP (see cleartool descr -l vob:\SRM_COMP for a list of those groups)
The path is somehow not selected by the current config spec.
It is best to do a cleartool ls in M:\yj73_SRDV3G_Proj_01_00_int\SRM_COMP\SRDV3G_Project\CRDB_V3\Application_Source\DAL to see how ClearCase displays obj.
The OP user1383839 confirms not using the right account for the Build Loop, which means it didn't benefit from the right environment variable, hence the "access denied" message.
Or you can also "runas" the project as a different user (see "Running cruise control.net under different credentials")
This issue got Fixed !:)
I was using the local account Previous
you need to go to the properties of the cruise control and change the account it is being used.
When I start the JBoss server to run my JSP page, it gives the error as:
Failed to create directory structure: C:\Program Files\jboss-4.2.2.GA\server\default\log
and then a pop-up appears saying
Starting JBoss v4.2 at localhost has encountered a problem.
Server JBoss v4.2 at localhost failed to start.
Please tell me what to do?
When starting for the first time for a certain configuration (here being default, if they are not already present, JBoss creates the directories:
$JBOSS_HOME\server\default\data
$JBOSS_HOME\server\default\log
$JBOSS_HOME\server\default\tmp
$JBOSS_HOME\server\default\work
These are used to store and write logs, temporary files and other various files generated.
There is obviously an error when it tries to create the log folder and this is most likely because it does not have permissions to write and create folders. ( Though you would get this every time since JBoss likes to write a lot of logs all the time ).
In Windows Vista/7, the Program Files folder is not (usually) write-able, so an application started by the user cannot create or modify anything there. You could run JBoss as Administrator but DON'T, it's a bad idea. All files which need to be created/modified by an application should usually be stored in the user's folder, Application Data or somewhere else on the hard drive.
Possible solutions:
Either install your JBoss server somewhere else where you have write access. ( It needs this also when running normally like for storing logs )
Configure JBoss to store logs and other files in different directories, outside of your normal Program Files one. For example to specify a different directory for logs you can set the JVM startup property jboss.server.log.dir ( Specify it at startup by using java -Djboss.server.log.dir=C:/I_can_write_here/. You can find the properties for other directories (and a lot more) at http://community.jboss.org/wiki/JBossProperties
The obvious thing to check is which, if any, of the directories in the quoted path are missing:
C:\Program Files\jboss-4.2.2.GA\server\default\log
Obviously, you have bigger problems than just this if C:\Program Files\ is missing, but you may have other directories missing.
You may need to run an initialize step to validate your configuration and create the directories.