unable to parse worker status

A

ahoi_

New Member
Apr 10, 2021
24
4
3
37
Hello,

checking the status of PBS 2 I am getting those errors:

Code: 
root@pb1:/ # systemctl status proxmox-backup-proxy.service proxmox-backup.service
● proxmox-backup-proxy.service - Proxmox Backup API Proxy Server
     Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2021-07-13 13:34:59 CEST; 10h ago
   Main PID: 514 (proxmox-backup-)
      Tasks: 10 (limit: 38279)
     Memory: 29.6G
        CPU: 8min 26.089s
     CGroup: /system.slice/proxmox-backup-proxy.service
             └─514 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy

Jul 13 23:37:08 pb1 proxmox-backup-proxy[514]: UPID:root1878:000001F9:00000854:00000000:60784477:termproxy::root@pam:'
Jul 13 23:37:13 pb1 proxmox-backup-proxy[514]: unable to parse worker status '
Jul 13 23:37:13 pb1 proxmox-backup-proxy[514]: UPID:root1878:000001F9:00000854:00000000:60784477:termproxy::root@pam: 6078448A OK' - unable to parse UPID '
Jul 13 23:37:13 pb1 proxmox-backup-proxy[514]: UPID:root1878:000001F9:00000854:00000000:60784477:termproxy::root@pam:'
Jul 13 23:37:23 pb1 proxmox-backup-proxy[514]: unable to parse worker status '
Jul 13 23:37:23 pb1 proxmox-backup-proxy[514]: UPID:root1878:000001F9:00000854:00000000:60784477:termproxy::root@pam: 6078448A OK' - unable to parse UPID '
Jul 13 23:37:23 pb1 proxmox-backup-proxy[514]: UPID:root1878:000001F9:00000854:00000000:60784477:termproxy::root@pam:'
Jul 13 23:37:28 pb1 proxmox-backup-proxy[514]: unable to parse worker status '
Jul 13 23:37:28 pb1 proxmox-backup-proxy[514]: UPID:root1878:000001F9:00000854:00000000:60784477:termproxy::root@pam: 6078448A OK' - unable to parse UPID '
Jul 13 23:37:28 pb1 proxmox-backup-proxy[514]: UPID:root1878:000001F9:00000854:00000000:60784477:termproxy::root@pam:'


Something to worry about?
 
what is your proxmox-backup-manager versions -v ?
 
Hi Dominik,

Code: 
# proxmox-backup-manager versions --verbose
proxmox-backup             2.0-1        running kernel: 5.11.22-1-pve
proxmox-backup-server      2.0.4-1      running version: 2.0.4       
pve-kernel-helper          7.0-4                                     
pve-kernel-5.11            7.0-3                                     
pve-kernel-5.11.22-1-pve   5.11.22-2                                 
ifupdown2                  3.0.0-1+pve5                             
libjs-extjs                7.0.0-1                                   
proxmox-backup-docs        2.0.4-1                                   
proxmox-backup-client      2.0.4-1                                   
proxmox-mini-journalreader 1.2-1                                     
proxmox-widget-toolkit     3.3-3                                     
pve-xtermjs                4.12.0-1                                 
smartmontools              7.2-pve2                                 
zfsutils-linux             2.0.4-pve1
 
thanks,

can you post the output of the following commands either as textfile or in '[ code ]' tags ?

Code: 
cat -A /var/log/proxmox-backup/tasks/archive
 
Sure. Unfortunately the output is too large for a post, so I attached a text-file.
 

Attachments

mhm.. ok for some reason the file contains some null bytes at the beginning of the second line (no idea how they could get there..., did your machine or processes crash? do you have maybe some unstable hardware?)
but to fix it you could open it with any editor (nano/vi/etc.) and remove the leading null bytes there, that should fix it
 
Hi,

the hardware or the process did never crash, but I updated to PBS 2 yesterday. If I understand that file correctly, it's some kind of archive of all tasks? So the second line would represent something on the very beginning of my PBS-usage?
 
no the files will be rotated into archive.1 archive.2.zstd etc. so it is just the 'most recent tasks'
but if you do not have a archive.1 etc. file, this would mean its one of the first tasks
 
Hi Dominik,

seems like it has never been rotated:

Code: 
find /var/log/proxmox-backup/ | grep archive
/var/log/proxmox-backup/tasks/archive

Code: 
stat /var/log/proxmox-backup/tasks/archive
 Datei: /var/log/proxmox-backup/tasks/archive
 Größe: 173157        Blöcke: 344        EA Block: 4096   reguläre Datei
 Gerät: 804h/2052d    Inode: 366216601   Verknüpfungen: 1
Zugriff: (0644/-rw-r--r--)  Uid: (   34/  backup)   Gid: (   34/  backup)
Zugriff: 2021-07-14 08:54:33.300132408 +0200
Modifiziert: 2021-07-14 10:52:25.048139808 +0200
Geändert: 2021-07-14 10:52:25.048139808 +0200
Geburt: 2021-04-15 15:14:00.000438494 +0200

The created-date is the first day I used PBS:

Code: 
Geburt: 2021-04-15 15:14:00.000438494 +0200

So in this case my guess is correct?



fyi: Rotation for /var/log/proxmox-backup/api is working fine:


Code: 
ls -lah /var/log/proxmox-backup/api/
insgesamt 288M
drwxr-xr-x 2 backup backup 4,0K 13. Jul 13:07 .
drwxr-xr-x 4 backup backup 4,0K 15. Apr 15:12 ..
-rw-r--r-- 1 backup backup  11M 14. Jul 11:06 access.log
-rw-r--r-- 1 backup backup 210M 13. Jul 13:07 access.log.1
-rw-r--r-- 1 backup backup 702K  2. Mai 00:00 access.log.10.zst
-rw-r--r-- 1 backup backup 812K 28. Apr 00:00 access.log.11.zst
-rw-r--r-- 1 backup backup 753K 24. Apr 00:00 access.log.12.zst
-rw-r--r-- 1 backup backup 2,7M 22. Jun 00:00 access.log.2.zst
-rw-r--r-- 1 backup backup 556K  4. Jun 00:00 access.log.3.zst
-rw-r--r-- 1 backup backup 531K 31. Mai 00:00 access.log.4.zst
-rw-r--r-- 1 backup backup 555K 27. Mai 00:00 access.log.5.zst
-rw-r--r-- 1 backup backup 793K 23. Mai 00:00 access.log.6.zst
-rw-r--r-- 1 backup backup 723K 19. Mai 00:00 access.log.7.zst
-rw-r--r-- 1 backup backup 582K 15. Mai 00:00 access.log.8.zst
-rw-r--r-- 1 backup backup 1,6M 11. Mai 00:00 access.log.9.zst
-rw-r--r-- 1 backup backup  22M 14. Jul 11:06 auth.log
-rw-r--r-- 1 backup backup  34M  3. Jul 23:59 auth.log.1
-rw-r--r-- 1 backup backup 548K  4. Jul 00:00 auth.log.2.zst
-rw-r--r-- 1 backup backup 559K 18. Jun 00:00 auth.log.3.zst
-rw-r--r-- 1 backup backup 543K  2. Jun 00:00 auth.log.4.zst
-rw-r--r-- 1 backup backup 505K 17. Mai 00:00 auth.log.5.zst
 
Last edited:
seems good. the task list only gets rotated if it grows too large so that seems fine.
as i said, to fix it remove the null bytes from the line (or remove the line if you do not need it)
 
Alright. For me it was important to check, whether this null byte has been written recently. As I interpret it, it was written right at the beginning and I can remember that the engineer who set up the PBS server mentioned that there was something wrong on the deployment image they used (some kind of custom build image the datacenter uses).

For me it's really important that this did not happen recently and all backups are valid. Prune, Garbage Collection and verification tasks are working fine, so I guess the fix of removing the line solves my problem and the system is still stable.
 
You must log in or register to reply here.
Top Bottom