Infos:

• Used Zammad version: 6.2.0-1704877727.2bda00c4.focal
• Used Zammad installation type: package
• Operating system: Ubuntu 20.04
• Browser + version: Brave, Edge, Firefox

The Instance runs on virtual mashine inside Virtual box. The host is Windows 10. After an automatic restart of the windows the zammad virtual mashine shows error 503 inside browser.

I know is not the best deployment but has worked fine since now. After a force restart due to update of windows we start the Virtual Box and and the virtual mashine and it just worked. Now i guess something went wrong due to the unexpected shutdown.

I tried update and upgrade, reboot multiple times without success.

Removed zammad and apache2 and installed them again.

Rebuilded the index in elastic (should have no role i did it anyway)

The logs from the apache show failing to connect to 127.0.0.1:3000. That is the loopback address and should rails be running on it if i am not mistaken:
[Fri Jan 12 12:58:11.766781 2024] [proxy:error] [pid 1057:tid 140234859714304] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed

[Fri Jan 12 12:58:11.766820 2024] [proxy_http:error] [pid 1057:tid 140234859714304] [client 192.168.178.39:60787] AH01114: HTTP: failed to make connection to backend: 127.0.0.1

[Fri Jan 12 12:58:12.489425 2024] [proxy:error] [pid 1057:tid 140234842928896] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed

[Fri Jan 12 12:58:12.489467 2024] [proxy_http:error] [pid 1057:tid 140234842928896] [client 192.168.178.39:60788] AH01114: HTTP: failed to make connection to backend: 127.0.0.1

The logs from Zammad seem fine to me:
I, [2024-01-12T12:58:49.805407#757-141700] INFO – : Running job thread for ‘Generate ‘Session’ data.’ (Sessions.jobs) status is: sleep
I, [2024-01-12T12:58:49.805659#757-141700] INFO – : Running job thread for ‘Execute planned jobs.’ (Job.run) status is: sleep

I saw no error there.

Here is my apache config for zammad
There i have not changed anything and is the default from zammad:
helpdeskadmin@helpdeskadmin:/etc/apache2/sites-available$ cat zammad.conf

this is the apache config for zammad

security - prevent information disclosure about server version

ServerTokens Prod

<VirtualHost *:80>
# replace ‘localhost’ with your fqdn if you want to use zammad from remote
ServerName localhost

## don't loose time with IP address lookups
HostnameLookups Off

## needed for named virtual hosts
UseCanonicalName Off

## configures the footer on server-generated documents
ServerSignature Off

ProxyRequests Off
ProxyPreserveHost On

<Proxy 127.0.0.1:3000>
    Require local
</Proxy>

ProxyPass /assets !
ProxyPass /favicon.ico !
ProxyPass /apple-touch-icon.png !
ProxyPass /robots.txt !
# legacy web socket server
ProxyPass /ws ws://127.0.0.1:6042/
# action cable
ProxyPass /cable ws://127.0.0.1:3000/cable
ProxyPass / http://127.0.0.1:3000/

# change this line in an SSO setup
RequestHeader unset X-Forwarded-User

DocumentRoot "/opt/zammad/public"

<Directory />
    Options FollowSymLinks
    AllowOverride None
</Directory>

<Directory "/opt/zammad/public">
    Options FollowSymLinks
    Require all granted
</Directory>

Running → journalctl -u zammad
Jan 12 09:26:29 helpdeskadmin systemd[1]: Started zammad.service.

Jan 12 10:25:28 helpdeskadmin systemd[1]: Stopping zammad.service…

Jan 12 10:25:28 helpdeskadmin systemd[1]: zammad.service: Succeeded.

Jan 12 10:25:28 helpdeskadmin systemd[1]: Stopped zammad.service.

Jan 12 10:25:28 helpdeskadmin systemd[1]: Started zammad.service.

Jan 12 11:55:53 helpdeskadmin systemd[1]: Stopping zammad.service…

Jan 12 11:55:53 helpdeskadmin systemd[1]: zammad.service: Succeeded.

Jan 12 11:55:53 helpdeskadmin systemd[1]: Stopped zammad.service.

Jan 12 11:56:13 helpdeskadmin systemd[1]: Started zammad.service.

Jan 12 11:59:39 helpdeskadmin systemd[1]: Stopping zammad.service…

Jan 12 11:59:39 helpdeskadmin systemd[1]: zammad.service: Succeeded.

Jan 12 11:59:39 helpdeskadmin systemd[1]: Stopped zammad.service.

– Reboot –

Jan 12 12:00:22 helpdeskadmin systemd[1]: Started zammad.service.

Jan 12 12:19:11 helpdeskadmin systemd[1]: Stopping zammad.service…

Jan 12 12:19:11 helpdeskadmin systemd[1]: zammad.service: Succeeded.

Jan 12 12:19:11 helpdeskadmin systemd[1]: Stopped zammad.service.

– Reboot –

Jan 12 12:19:56 helpdeskadmin systemd[1]: Started zammad.service.

Jan 12 12:33:44 helpdeskadmin systemd[1]: Stopping zammad.service…

Jan 12 12:33:44 helpdeskadmin systemd[1]: zammad.service: Succeeded.

Jan 12 12:33:44 helpdeskadmin systemd[1]: Stopped zammad.service.

– Reboot –

Jan 12 12:34:29 helpdeskadmin systemd[1]: Started zammad.service.

lines 279-328/328 (END)

Running sudo netstat -tlpen shows:
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 114 28935 959/mysqld
tcp 0 0 127.0.0.1:587 0.0.0.0:* LISTEN 0 26599 1164/sendmail: MTA:
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 116 26903 1022/redis-server 1
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 21416 688/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 25745 889/sshd: /usr/sbin
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 26598 1164/sendmail: MTA:
tcp 0 0 127.0.0.1:6042 0.0.0.0:* LISTEN 997 29248 755/script/websocke
tcp6 0 0 :::443 :::* LISTEN 0 27785 1056/apache2
tcp6 0 0 ::1:6379 :::* LISTEN 116 26904 1022/redis-server 1
tcp6 0 0 127.0.0.1:9200 :::* LISTEN 115 48424 5675/java
tcp6 0 0 ::1:9200 :::* LISTEN 115 48423 5675/java
tcp6 0 0 :::80 :::* LISTEN 0 27781 1056/apache2
tcp6 0 0 127.0.0.1:9300 :::* LISTEN 115 47686 5675/java
tcp6 0 0 ::1:9300 :::* LISTEN 115 47679 5675/java
tcp6 0 0 :::22 :::* LISTEN 0 26760 889/sshd: /usr/sbin

soo no port 3000

I tried restarting zammad services both with restart and with stop+start:
helpdeskadmin@helpdeskadmin:/etc/apache2/sites-available$ systemctl status zammad
● zammad.service
Loaded: loaded (/etc/systemd/system/zammad.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2024-01-12 13:54:09 UTC; 20s ago
Main PID: 26416 (sleep)
Tasks: 1 (limit: 9426)
Memory: 192.0K
CGroup: /system.slice/zammad.service
└─26416 /bin/sleep infinity

Jan 12 13:54:09 helpdeskadmin systemd[1]: Started zammad.service.
helpdeskadmin@helpdeskadmin:/etc/apache2/sites-available$ systemctl status zammad-web
● zammad-web.service
Loaded: loaded (/etc/systemd/system/zammad-web.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2024-01-12 13:54:09 UTC; 30s ago
Main PID: 26417 (sleep)
Tasks: 1 (limit: 9426)
Memory: 208.0K
CGroup: /system.slice/zammad-web.service
└─26417 /bin/sleep infinity

Jan 12 13:54:09 helpdeskadmin systemd[1]: Started zammad-web.service.
helpdeskadmin@helpdeskadmin:/etc/apache2/sites-available$ systemctl status zammad-websocket
● zammad-websocket.service
Loaded: loaded (/etc/systemd/system/zammad-websocket.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2024-01-12 13:54:09 UTC; 43s ago
Main PID: 26419 (sleep)
Tasks: 1 (limit: 9426)
Memory: 220.0K
CGroup: /system.slice/zammad-websocket.service
└─26419 /bin/sleep infinity

Jan 12 13:54:09 helpdeskadmin systemd[1]: Started zammad-websocket.service.

I also have ran:
helpdeskadmin@helpdeskadmin:/etc/apache2/sites-available$ sudo zammad config:get ZAMMAD_RAILS_PORT
3000

I even made a fresh install of zammad on new virtual mashine and tried to compare config files but i could not see any issue.

Any help will be appriciated and thank you in advance. Zammad is a great Open source Software

Expected behavior:

Running after starting after an unexpected shutdown

Actual behavior:

*Showing error 503 and unable to connect to loopback on port 3000

Steps to reproduce the behavior:

I guess plug the mashine out of the electricity and start it