Page 1 of 1

Processmaker can not start

Posted: Tue Mar 27, 2018 1:17 pm
by jornig
Hi people,

I am not being able to start Processmaker after we have a issue with the disk drive empty space, we was able to free up disk space.
But now we are getting this error in the apache logs:

[Tue Mar 27 11:01:33 2018] [notice] Apache/2.2.29 (Win32) mod_ssl/2.2.29 OpenSSL/1.0.1i PHP/5.3.29 configured -- resuming normal operations
[Tue Mar 27 11:01:33 2018] [notice] Server built: Aug 28 2014 16:28:52
[Tue Mar 27 11:01:33 2018] [notice] Distributed by: The Apache Haus
[Tue Mar 27 11:01:33 2018] [notice] Compiled with: Visual Studio 2008
[Tue Mar 27 11:01:33 2018] [notice] Parent: Created child process 5024
[Tue Mar 27 11:01:34 2018] [notice] Child 5024: Child process is running
[Tue Mar 27 11:01:34 2018] [notice] Child 5024: Acquired the start mutex.
[Tue Mar 27 11:01:34 2018] [notice] Child 5024: Starting 64 worker threads.
[Tue Mar 27 11:01:34 2018] [notice] Child 5024: Starting thread to listen on port 443.
[Tue Mar 27 11:01:34 2018] [notice] Child 5024: Starting thread to listen on port 443.
[Tue Mar 27 11:01:34 2018] [notice] Child 5024: Starting thread to listen on port 80.
[Tue Mar 27 11:01:34 2018] [notice] Child 5024: Starting thread to listen on port 80.
[Tue Mar 27 11:01:54 2018] [error] [client 172.0.0.0] PHP Fatal error: Call to a member function getAttributes() on a non-object in C:\\opt\\processmaker\\workflow\\public_html\\sysGeneric.php on line 690
[Tue Mar 27 11:01:58 2018] [error] [client 172.0.0.0] PHP Fatal error: Call to a member function getAttributes() on a non-object in C:\\opt\\processmaker\\workflow\\public_html\\sysGeneric.php on line 690


Any help will be appreciate

Re: Processmaker can not start

Posted: Tue Mar 27, 2018 3:43 pm
by AlanBueno
Hello,

Could you please explain how exactly you freed up space in your disk drive? a possible cause for this problem might be accidentally messing with one of Processmaker components or permissions, try restarting apache and also deleting your browser cache or accessing Processmaker through an incognito window.

Re: Processmaker can not start

Posted: Tue Mar 27, 2018 5:40 pm
by amosbatto
Are you using Linux? You may have deleted the files, but the file system has not yet freed the space. Read this discussion of the problem:
https://unix.stackexchange.com/question ... -files-now

I had this problem once and I had to reboot the server to force the file system to free the space.

Re: Processmaker can not start

Posted: Mon Apr 23, 2018 9:57 am
by calman
Any resolution found to this? I believe we have a similar issue.

Thanks

Re: Processmaker can not start

Posted: Mon Apr 23, 2018 4:16 pm
by amosbatto
calman wrote:Any resolution found to this? I believe we have a similar issue.
Are you using Linux? Post the output of these two commands:
Code: Select all
fdisk -l
dumpe2fs -h /dev/sda1
Change sda1 to the name of the partition where you have ProcessMaker installed. Also, try rebooting to force the operating system to free up the space from deleted files.