OPen lite speed server gives 503 Service Unavailable The server is temporarily busy

taker18

taker18

Verified User
Joined
Oct 18, 2021
Messages
141
Location
USA
fresh installation than after trying installing open lite speed I got

503 Service Unavailable The server is temporarily busy, try again later!​

However the Log file says
2024-05-18 23:17:35.461877 [ERROR] [658179] Hostname [*] on listener [[IP6]:80] is mapped to virtual host [[IP6]], can't map to virtual host [hostname]!
2024-05-18 23:17:35.461880 [ERROR] [658179] Hostname [*] on listener [IP6]:443] is mapped to virtual host [[IP6]], can't map to virtual host [hostname]!

something is not listing
trouble shooting that already done:
1- I switchback to Apach and back to open lite speed still not working
2- PHP in memory is 128
3- this is the command line that i used to switch to open lite speed


cd /usr/local/directadmin/custombuild

./build update
./build set webserver openlitespeed
./build set mod_ruid2 no
./build set php1_mode lsphp
./build set php1_release 8.1
./build openlitespeed
./build php
./build rewrite_confs

any idea please
 
gate2vn said:
You can ignore that log. But check in stderr.log, is there anything?
Click to expand...
sorry late reply,
here is what i got

2024-05-19 00:11:18.518962 [ERROR] [661414] Hostname [*] on listener [Ip6:80] is mapped to virtual host [IP4], can't map to virtual host [hostname]!

2024-05-19 00:11:18.518983 [ERROR] [661414] Hostname [*] on listener [IP6:443] is mapped to virtual host [IP4], can't map to virtual host [hostname]!

2024-05-19 00:11:18.518988 [ERROR] [661414] Hostname [*] on listener [[IP6]:80] is mapped to virtual host [[IP6]], can't map to virtual host [hostname]!

2024-05-19 00:11:18.518991 [ERROR] [661414] Hostname [*] on listener [[IP6]:443] is mapped to virtual host [[IP6]], can't map to virtual host [hostname]!
 
I decided to switch back to Apache. I have been using open speed and no issue, but the supported community of Apache is much stronger and I am not sure really that open lite speed will make that huge of the different. if I am getting an error and the Papche is working out of the box with no issue. why not.
both are good choices but i will go with the easy one.

thank you for the help

./build update
./build set webserver apache
./build set php1_mode php-fpm
./build set php1_release 8.1
./build set mod_ruid2 yes
./build apache
./build php
./build rewrite_confs


the only issue with the command that when i switched to open lite speed i switch Mod_ruid off with ./build set mod_ruid2 no.
but when I am trying to turn on with ./build set mod_ruid2 yes gives me a message that yes is not supported

yes is not a valid setting for mod_ruid2 option.
how can i make sure that is working ?

root@server ~# systemctl status httpd
● httpd.service - The Apache HTTP Server
Loaded: loaded (/etc/systemd/system/httpd.service; enabled; preset: disabled)
Active: active (running) since Sun 2024-05-19 19:00:18 CDT; 11min ago
Process: 926693 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS)
Main PID: 925528 (httpd)
Status: "Total requests: 16; Idle/Busy workers 100/0;Requests/sec: 0.0243; Bytes served/sec: 14 B/sec"
Tasks: 279 (limit: 407269)
Memory: 62.0M
CPU: 454ms
CGroup: /system.slice/httpd.service
├─925528 /usr/sbin/httpd -DFOREGROUND
├─926980 /usr/sbin/httpd -DFOREGROUND
└─926982 /usr/sbin/httpd -DFOREGROUND

May 19 19:00:18 server.domain.com systemd[1]: Starting The Apache HTTP Server...
May 19 19:00:18 server.domain.com systemd[1]: Started The Apache HTTP Server.
May 19 19:00:27 server.domain.com systemd[1]: Reloading The Apache HTTP Server...
May 19 19:00:27 server.domain.com systemd[1]: Reloaded The Apache HTTP Server.

that looks like is working for me, I hope so
Thank you All
 
taker18 said:
503 Service Unavailable The server is temporarily busy, try again later!
Click to expand...

As of the error, you might check first .htaccess files for possible conflicts - most likely it is the culrpit. Then check other things like the following:

- rename the file .htaccess and see how a site opens
- try plain files: images, css, js - and see whether or not they give HTTP/503 error too.
- as of php scripts - check a simple PHP script with <?phpinfo();?> inside outside CMS engine.
- as of CMS, you might try and check addons, modules, PHP ini settings, assigned memory for PHP

So, steps by step you might check which script or URLs fails. There is no other way to debug I believe.

If it is too complicated - you may stick to Apache, or hire Poralix for it.
 
You must log in or register to reply here.
Back
Top