I suggest checking manually on the status of the backuppc server. On my
linux box, I do, as root,
systemctl status backuppc
to get some reassuring feedback (or not :-)). Instead of "status", you
can also do "start" and other commands outlined in the "-h" option. If
the status shows not running, the feedback from the "start" command
might indicate why. The "-l" flag gives more details.
On 2022-12-02 12:27, Mister Ed wrote:
So, I did create that user and I still do not get a webui... here are
my logs from a fresh restart.
2022-12-02.14:24:03 [NOTICE] ** [container-init] Detected Container
that has been restarted - Cleaning '/tmp/.container' files
2022-12-02.14:24:03 [NOTICE] ** [monitoring] Container configured for
monitoring with 'zabbix modern'
2022-12-02.14:24:03 [NOTICE] ** [scheduling] Container configured for
scheduled tasks with 'cron'
2022-12-02.14:24:03 [NOTICE] ** [messaging] Container configured to
route mail via SMTP to 'postfix-relay'
2022-12-02.14:24:04 [NOTICE] ** [backuppc] First run of the container.
BackupPC will be installed.
2022-12-02.14:24:04 [NOTICE] ** [backuppc] If exist, configuration and
data will be reused and upgraded as needed.
2022-12-02.14:24:04 [INFO] ** [backuppc] Container initialization complete
2022-12-02.14:24:04 [STARTING] ** [fcgiwrap] [1] Starting fcgiwrap
2022-12-02.14:24:04 [STARTING] ** [nginx] [1] Starting nginx 1.23.2
2022-12-02.14:24:04 [STARTING] ** [backuppc] [1] Starting BackupPC 4.4.0
2022-12-02.14:24:04 [STARTING] ** [monitoring] [1] Starting Zabbix
Agent (modern) 6.2.4
2022-12-02.14:24:04 [STARTING] ** [scheduling] [1] Starting cron
2022-12-02.14:24:05 [STARTING] ** [backuppc] [2] Starting BackupPC 4.4.0
omitted 3-49 to keep this shorter.
2022-12-02.14:24:53 [STARTING] ** [backuppc] [50] Starting BackupPC 4.4.0
2022-12-02.14:24:54 [ERROR] ** [backuppc] POTENTIAL RUNWAY
DETECTECTED: Disabling 20-backuppc service because it has tried
restarting '50' times
On Fri, Dec 2, 2022 at 2:22 PM Norman J. Goldstein <norm...@telus.net>
wrote:
It is my understanding that most installers create the user,
"backuppc". If logging out and back in does not fix this, then the
docker installation omitted this step. Creating the user, manually,
should fix this.
On 2022-12-02 09:41, Mister Ed wrote:
> I have installed the BackupPC docker container on my Unraid server
> running version 6.11.5 and it is failing to start. I have never
run
> this application and it looks very useful as it should handle my
linux
> and windows systems.
>
> I think the problem is likely at the top of my logs, but I am
not sure
> if I need to create a user or use the existing root user...
>
> chown: unknown user backuppc
> chown: unknown user/group backuppc:backuppc
> tar: can't open 'BackupPC-4.4.0.tar.gz': No such file or directory
> /etc/cont-init.d/20-backuppc: line 33: cd:
/usr/src/BackupPC-4.4.0: No
> such file or directory
>
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: https://github.com/backuppc/backuppc/wiki
> Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project:https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
