Dan, Thanks so much for your response...to be honest I didn't think I would get one.
Upon further diffing I tracked down /etc/php.ini which looks to what needs to be updated. I was being told that only post_max_size needed to be updated but totally agree that upload_max_filesize also should be updated. Trick now would be to get sudo to enable me to do this or find an admin who can copy an updated version I made into /etc. In regards to restarting Apache...again dumb question, but does apache get restarted when the scheduler is restarted or much it be restarted separately? Frankly I have never done anything with apache. (and the big unfortunately is when I was given fossology to support I was told not to spend any time on it learning anything but just to respond to issues as they arise...so every time there is an issue it's an adventure!) My plan would be to initially increase the size of these 2 properties to 4096M, restart the scheduler(fossology), and test. If OK, update the properties to a size to accommodate the large file they are trying to process and repeat the above. I don't think I'll leave it at that size, 16384M, but would probably put it back to 4096M. Thanks!!!!! Charlie -----Original Message----- From: Stangel, Dan [mailto:dan.stan...@hpe.com] Sent: Wednesday, January 9, 2019 11:33 AM To: Kline, Charles (US) <charles.kl...@lmco.com>; fossol...@fossology.org Subject: EXTERNAL: RE: Question on version 2.5.0 Hi Charlie, On 2018-01-08, Kline, Charles wrote: > Yeah, I know...why are we still using 2.5.0...long story. Don't feel too bad - we're still on 2.6.2 for our production instance (again, long story.. Suffice it to say these releases have a long lifespan) > Question....users want to process/upload files greater than 2GB which > my users are saying is the largest then can process. Trying to > figure out the correct place to update this value. > > In > /app/fossology/fossology_2.5/share/fossology/lib/php/common-scheduler. > php > there is the following... > common-scheduler.php: \param $MaxSize - optional max read size, > default is 2048 common-scheduler.php:function > fo_scheduler_read($SchedObj, $MaxSize=2048) I assume this is in MB > > But in the fossology online info I am seeing this...assuming these are > values for the latest version of fossology...in the link they talk > about updating php.ini for > apache...(http://archive15.fossology.org/projects/fossology/wiki/SysCo > nfig/annotate/9) > (...) > So trying to figure out where I actually need to make an update to > change the size of the file that can be uploaded/processed by the users. You should only need to update the upload_max_filesize and post_max_size parameters in your php.ini file. In our case for example, we have ; Maximum allowed size for uploaded files. ; http://php.net/upload-max-filesize upload_max_filesize = 4096M ; Maximum size of POST data that PHP will accept. ; http://php.net/post-max-size post_max_size = 4096M Once you have updated php.ini, just be sure to restart Apache to pick up the changes. Then try to do a > 2G upload from file (ideally from a client that isn't too far away, network-wise) to verify that it works. Dan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3199): https://lists.fossology.org/g/fossology/message/3199 Mute This Topic: https://lists.fossology.org/mt/28983424/21656 Group Owner: fossology+ow...@lists.fossology.org Unsubscribe: https://lists.fossology.org/g/fossology/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
