Hi Mark, Sorry we don’t test with suse. Any volunteers?
The simplest solution for mimetype is to just not use it. You don’t need it for license, copyrights or buckets. So if everything else, except mimetype ran, you are in good shape. php.ini would have no effect since the agents are not written in php. You said you are able to “partially load larger tar files”, but then say that mimetype doesn’t run. If the other scanners ran, then the upload must have completed successfully. The upload is done by wget_agent, ununpack, and adj2nest. After the upload is done the scanners can run (or be rerun). We frequently run very large uploads (sometimes iso’s north of 10 GB). So this shouldn’t be a size issue. Bob Gobeille On May 20, 2014, at 7:38 AM, Felton, Mark <[email protected]> wrote: > Thanks to everyone who replied. I was able to get the fossjob working by > putting a symbolic link to fossjob in /usr/bin. Apparently my path to it was > not being found in /usr/local/bin/fossjobs. > This may due to the complexity of building with the tar file on my suse > linux. I have gotten much further but now have a new issue to work. I am able > to upload smaller tar files from the server.These go all the way to > completion. > I have buckets turned off for now. > I am also able to partially load larger tar files (my total code base), but > once they upload they get stuck in the mime type agent. > This was not true with the smaller ones. The mime type agent queued and was > scheduled but that was as far as it got. > I waited a full day and no change. I increased php.ini max upload time, do I > need to also increase memory (or something else). If yes what is a reasonable > value?
_______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
