Lamp is not staring anymore

pnemenz · November 8, 2025, 7:26am

NethServer Version: 8
Module: Lamp

I have two Lamp instances running on my NS8 Node.

one of them isn’t staring anymore.

The Logs shows:

2025-11-08T07:58:27+01:00 [1:lamp3:podman] lamp
2025-11-08T07:58:27+01:00 [1:lamp3:systemd] Started Podman lamp.service.
2025-11-08T07:58:27+01:00 [1:lamp3:systemd] Starting Podman  apache2-app.service...
2025-11-08T07:58:28+01:00 [1:lamp3:lamp3] agent.ldapproxy: domain ad.xxxx.at should not be used by lamp3. Invoke agent.bind_user_domains(["ad.xxxx.at"]) to fix this warning.
2025-11-08T07:58:28+01:00 [1:lamp3:lamp3] Error: lsetxattr(label=system_u:object_r:container_file_t:s0:c644,c930) /home/lamp3/.local/share/containers/storage/volumes/app/_data/modules_v4/reminder: operation not permitted
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] apache2-app.service: Control process exited, code=exited, status=126/n/a
2025-11-08T07:58:28+01:00 [1:lamp3:lamp3] cb56b9978e7618af9af6a92cabdef26e323d6f83c9de89897591e66266e4e7f5
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] apache2-app.service: Failed with result 'exit-code'.
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] Failed to start Podman  apache2-app.service.
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] apache2-app.service: Consumed 1.119s CPU time.
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] apache2-app.service: Scheduled restart job, restart counter is at 20.
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] Stopped Podman  apache2-app.service.
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] apache2-app.service: Consumed 1.119s CPU time.
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] Stopping Podman lamp.service...
2025-11-08T07:58:28+01:00 [1:lamp3:systemd] Removed slice cgroup user-libpod_pod_148dc73ef3432f1e670ed215306964c6d6fce769bf78e40bc49b9ca5ec484352.slice.

when trying to start apache2

 podman run --name apache2-app
Error: requires at least 1 arg(s), only received 0
[lamp3@ns8 state]$ systemctl --user start apache2-app
Job for apache2-app.service failed because the control process exited with error code.
See "systemctl --user status apache2-app.service" and "journalctl --user -xeu apache2-app.service" for details.

systemctl --user status apache2-app.service

 apache2-app.service - Podman  apache2-app.service
     Loaded: loaded (/home/lamp3/.config/systemd/user/apache2-app.service; disabled; preset: disabled)
     Active: inactive (dead) (Result: exit-code) since Sat 2025-11-08 06:58:28 UTC; 18min ago
    Process: 16921 ExecStartPre=/bin/rm -f /run/user/1015/apache2-app.pid /run/user/1015/apache2-app.ctr-id (code=exited, status=0/SUCCESS)
    Process: 16922 ExecStartPre=runagent discover-smarthost (code=exited, status=0/SUCCESS)
    Process: 16935 ExecStartPre=runagent discover-ldap (code=exited, status=0/SUCCESS)
    Process: 16936 ExecStartPre=/bin/mkdir -vp initdb.d crontabs (code=exited, status=0/SUCCESS)
    Process: 16937 ExecStart=/usr/bin/podman run --conmon-pidfile /run/user/1015/apache2-app.pid --cidfile /run/user/1015/apache2-app.ctr-id --cgroups=no-conmon --pod-id-file /run/user/1015/lamp.pod->
    Process: 16949 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/user/1015/apache2-app.ctr-id (code=exited, status=0/SUCCESS)
        CPU: 1.119s

ournalctl --user -xeu apache2-app.service
Hint: You are currently not seeing messages from the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.

It did work before, I can’t say when it stoped, I don’t use this particular application much.

What can I do now?

stephdl · November 8, 2025, 9:20am

2025-11-08T07:58:28+01:00 [1:lamp3:lamp3] Error: lsetxattr(label=system_u:object_r:container_file_t:s0:c644,c930) /home/lamp3/.local/share/containers/storage/volumes/app/_data/modules_v4/reminder: operation not permitted

what is that ?

stephdl · November 8, 2025, 9:21am

this is the official mount point

github.com/stephdl/ns8-lamp

imageroot/systemd/user/apache2-app.service

421f315eb


      
          WorkingDirectory=%S/state
          Restart=always
          TimeoutStopSec=70
          ExecStartPre=/bin/rm -f %t/apache2-app.pid %t/apache2-app.ctr-id
          ExecStartPre=-runagent discover-smarthost
          ExecStartPre=-runagent discover-ldap
          ExecStartPre=/bin/mkdir -vp initdb.d crontabs
          ExecStart=/usr/bin/podman run --conmon-pidfile %t/apache2-app.pid \
              --cidfile %t/apache2-app.ctr-id --cgroups=no-conmon \
              --pod-id-file %t/lamp.pod-id --replace -d --name  apache2-app \
              --volume mysql:/var/lib/mysql:Z \
              --volume app:/app:Z \
              --volume ./initdb.d:/initdb.d:Z \
              --volume ./conf.d/mysql.cnf:/etc/mysql/conf.d/mysql.cnf:Z \
              --volume ./conf.d/mysqldump.cnf:/etc/mysql/conf.d/mysqldump.cnf:Z \
              --volume ./crontabs:/var/spool/cron/crontabs:Z \
              --env SMTP_* \
              --env LAMP_* \
              --env CREATE_MYSQL_USER=${CREATE_MYSQL_USER} \
              --env MYSQL_USER_NAME=${MYSQL_USER_NAME} \
              --env MYSQL_USER_DB=${MYSQL_USER_DB} \

pnemenz · November 8, 2025, 9:53am

This is a modul of the installed application, its webtrees (https://webtrees.net/). The app installed its by itself, so I dont’t know how more about it. should I thry to remove this plugin?

stephdl · November 8, 2025, 9:56am

I suspect a permission issue, go inside the container and check the permission

capote · November 8, 2025, 10:20am

I also use webtrees within lamp. But I don’t understand what you mean with “by itself” and “plugin”. Could you elaborate it?

I simply created a subdirectory in the root directory, copied the scripts, and installed webtrees.

https://www.myancestry.de

embedded in WordPress

direct link: ...MyAncestry – myAncestry - Genealogie der Familien Bernd, Dargel, Prescher, Klepp, Wendenburg u.a.

pnemenz · November 8, 2025, 10:49am

Changed the permissions in the foder to 665. Now the error isn’t coming anymore. but lamp is still not starting.

pnemenz · November 8, 2025, 10:57am

I installed the module reminder. Looks like there is something wrong with that (or my insallation). I just removed it and now LAMP and webtrees are working again.

Thank you for your help