Search results

Hi @jivy26 Do you see anything in our stderr.log or in any php error logs? Kevin

Glad to hear you were able to get it working! If you don't mind explaining, what issues did you encounter when trying to set this up? Cheers, Kevin

Hi @jivy26 Please check the vhost's configurations to make sure you're using the correct PHP version. The PHPInfo you sent is using PHP Version 7.0.22-1+xenial The output above is for lsphp71.

Glad to hear it! Let us know if you run into any more issues, we're always happy to help!

Hi @Rudi, First off, please make sure that nothing else is listening on the same port. in the server configurations, please check to see that the log level is set to DEBUG and HIGH. After that, try starting the server and check the log. There should be some log messages regarding attempting...

Hi @jivy26 Apologies for the delay. Please run the following command: dpkg -l | grep lsphp and see if lsphp70-curl is listed. If it is, try restarting the server again to see if it picks up the package. If it's not listed, then it's not installed, maybe see if the apt-get command resulted...

Could you send us your phpinfo output? You can send it to me via conversation if you'd rather the information not be public.

Hi @jivy26 Ols1click will not include all the packages automatically. Running the following command should grab curl for you: apt-get install lsphpXX-curl Replacing XX with php version. Cheers, Kevin

As mentioned in the other thread, this issue should be resolved in the next release. Both are permission/ownership issues, so hopefully the next release will resolve that. Cheers, Kevin

Thanks for the info. This issue should be resolved in the next release. Cheers, Kevin

Hi @Jamie-VV So what this is trying to do is check for new releases. If it finds a new release, it will append a log message to let you know that there is a new release. With regards to who should own this directory, what OS are you using? and who do you have configured to run the server as...

They cache information for later in case it is needed again. These specific ones are for dns.

Well, until it creates a core file, unfortunately, we cannot do much to figure out what the issue is. Please try deleting the contents of /dev/shm/ols in the meantime and restart the server, hopefully the issue will present itself.

That message is because you are trying to run OLS as root. Please try changing to running as nobody:nobody or nobody:nogroup

Just to confirm, you have gdb installed there correct? In that case, yeah - it looks like it's trying to create a core file, but did not yet.

Hi @slowaways Can you confirm taht you have the following packages installed? build-essential libpcre3-dev libexpat1-dev libssl-dev libgeoip-dev zlib1g-dev curl Cheers, Kevin

once outputted, you can type 'quit' to quit.

Please check /tmp/lshttpd/ (maybe bak-core). There is likely a core file there. If the timestamp matches about the time OLS stopped working, it was probably generated by that issue. If this is the case, please open a private conversation with me and send me the output after the following...

Hi @ckissi Did you get a core dump from when this occurred? It could be a SHM corruption. There should have been a core file generated based on the ps output. Cheers, Kevin

Hey there @jivy26 That's some good stuff there! If you still have any questions about the set up let us know! Cheers, Kevin