Hi,
I'm freshly installing the latest Yioop version.
I built a new CentOS 7.3.1611 server, added an Apache virtual server running under mod_fcgi, php 5.4, etc.
I then git cloned yioop, put it into the main web directory, fixed the AllowOverride, went into the web interface of the /admin.
The questions i have are:
1. The main web directory shows me a blank page, which is odd, nothing I could see in Apache logs to indicate any problems (usually blank pages are php errors or the like)
2. I got into the /admin path, started to configure based on your Install guide on-line. I turn ON queueserver and fetcher, nothing in logs. I turn on media server, log file generated.
I then try the CLI approach using:
php QueueServer.php terminal
and jumps back to the shell prompt immediately. Same goes for php Fetcher.php terminal.
Using terminal, I would expect it to sit there until I press CTRL-C (as documented).
So something is wrong and debugging it is difficult when no output is produced.
So for point 2, how can I debug this ?
Or maybe this doesn't work too well under mod_fcgi ? - note that permissions on the files and directories are completely owned by the mod_fcgi user/group.
Any advice?
Thanks.
Hi,
I'm freshly installing the latest Yioop version.
I built a new CentOS 7.3.1611 server, added an Apache virtual server running under mod_fcgi, php 5.4, etc.
I then git cloned yioop, put it into the main web directory, fixed the AllowOverride, went into the web interface of the /admin.
The questions i have are:
1. The main web directory shows me a blank page, which is odd, nothing I could see in Apache logs to indicate any problems (usually blank pages are php errors or the like)
2. I got into the /admin path, started to configure based on your Install guide on-line. I turn ON queueserver and fetcher, nothing in logs. I turn on media server, log file generated.
I then try the CLI approach using:
php QueueServer.php terminal
and jumps back to the shell prompt immediately. Same goes for php Fetcher.php terminal.
Using terminal, I would expect it to sit there until I press CTRL-C (as documented).
So something is wrong and debugging it is difficult when no output is produced.
So for point 2, how can I debug this ?
Or maybe this doesn't work too well under mod_fcgi ? - note that permissions on the files and directories are completely owned by the mod_fcgi user/group.
Any advice?
Thanks.