proxmox-backup-proxy not working on fresh install of pbs 3.2 upgraded to 3.4

F

fsalas

Renowned Member
Sep 9, 2014
13
0
66
Hi, I'm having this problem installing pbs, after install and reboot of pbs 3.2, no web gui, updated to 3.4 does not fix it

systemctl status proxmox-backup-proxy output is this

Sep 11 17:47:06 pbsOffline2 systemd[1]: Started session-3.scope - Session 3 of User root.
Sep 11 17:47:06 pbsOffline2 sshd[862]: pam_env(sshd:session): deprecated reading of user environment enabled
Sep 11 17:48:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:49:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:50:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:51:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:51:44 pbsOffline2 smartd[512]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 54 to 56
Sep 11 17:51:55 pbsOffline2 proxmox-backup-proxy[691]: rrd journal successfully committed (17 files in 0.030 seconds)
Sep 11 17:52:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:53:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:54:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:54:14 pbsOffline2 systemd[1]: Starting proxmox-backup-daily-update.service - Daily Proxmox Backup Server update and maintenance activities...
Sep 11 17:54:32 pbsOffline2 systemd[1]: proxmox-backup-daily-update.service: Deactivated successfully.
Sep 11 17:54:32 pbsOffline2 systemd[1]: Finished proxmox-backup-daily-update.service - Daily Proxmox Backup Server update and maintenance activities.
Sep 11 17:54:32 pbsOffline2 systemd[1]: proxmox-backup-daily-update.service: Consumed 9.184s CPU time.
Sep 11 17:55:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:56:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:57:00 pbsOffline2 proxmox-backup-proxy[691]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobsta>
Sep 11 17:57:12 pbsOffline2 proxmox-backup-proxy[691]: Internal Hyper error, please report InvalidHeaderName
Sep 11 17:57:28 pbsOffline2 systemd[1]: Stopping proxmox-backup-proxy.service - Proxmox Backup API Proxy Server...
Sep 11 17:57:28 pbsOffline2 systemd[1]: proxmox-backup-proxy.service: Deactivated successfully.
Sep 11 17:57:28 pbsOffline2 systemd[1]: Stopped proxmox-backup-proxy.service - Proxmox Backup API Proxy Server.
Sep 11 17:57:28 pbsOffline2 systemd[1]: proxmox-backup-proxy.service: Consumed 12.131s CPU time.
Sep 11 17:57:28 pbsOffline2 systemd[1]: Starting proxmox-backup-proxy.service - Proxmox Backup API Proxy Server...
Sep 11 17:57:28 pbsOffline2 proxmox-backup-proxy[1439]: catching shutdown signal
Sep 11 17:57:28 pbsOffline2 proxmox-backup-proxy[1439]: catching reload signal
Sep 11 17:57:28 pbsOffline2 systemd[1]: Started proxmox-backup-proxy.service - Proxmox Backup API Proxy Server.
Sep 11 17:57:28 pbsOffline2 proxmox-backup-proxy[1439]: applied rrd journal (580 entries in 0.051 seconds)
Sep 11 17:57:28 pbsOffline2 proxmox-backup-proxy[1439]: rrd journal successfully committed (17 files in 0.030 seconds)
Sep 11 17:57:44 pbsOffline2 proxmox-backup-proxy[1439]: Internal Hyper error, please report InvalidHeaderName
Sep 11 17:57:54 pbsOffline2 proxmox-backup-proxy[1439]: thread 'tokio-runtime-worker' panicked at /usr/share/cargo/registry/hyper-0.14.32/src/proto/h1/role.rs:264:43:
Sep 11 17:57:54 pbsOffline2 proxmox-backup-proxy[1439]: range end index 681 out of range for slice of length 675
Sep 11 17:57:54 pbsOffline2 proxmox-backup-proxy[1439]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Sep 11 17:57:55 pbsOffline2 proxmox-backup-proxy[1439]: Internal Hyper error, please report InvalidHeaderName
Sep 11 17:58:00 pbsOffline2 proxmox-backup-proxy[1439]: could not get last run time of logrotate access-log_and_task-archive: unable to read '"/var/lib/proxmox-backup/jobst>
Sep 11 17:58:00 pbsOffline2 proxmox-backup-proxy[1439]: Internal Hyper error, please report InvalidHeaderName

tried also to do an upgrade to pbs 4 that ended in a Segfault at libssl

This is a small PC I'm using for secondary offsite backup mirror.

thanks in advance for any tip.

Fernando
 
that sounds like the machine might have bigger issues.. please check disk and memory for hardware problems, in particular!
 
You must log in or register to reply here.
Top Bottom