[Piuparts-reports] Cron <piupartsm at pejacevic> detect_piuparts_issues
Cron Daemon
root at pejacevic.debian.org
Sat Oct 21 05:50:53 UTC 2017
Runtime: 00:05:49
piuparts problems detected!
(By grep'ing for
PIUPARTS OUTPUT INCOMPLETE
WARNING: History of available packages does not match - reference chroot may be outdated
tar( \(child\))?: .*.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
gzip: stdin: invalid compressed data--crc error
ERROR:.*:Temporary directory is not a directory
E: Sub-process Popen returned an error code \(2\)
chroot: failed to run command '.*': Permission denied
ERROR: Command failed \(status=(-7|100)\): .* 'apt-cache'
update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: Invalid argument
userdel: user .* is currently logged in
NO SPACE LEFT ON DEVICE
No space left on device
E: You don't have enough free space in /var/cache/apt/archives/
E: Failed to write temporary StateFile /var/lib/apt/extended_states.tmp
tar: .*: Wrote only .* of .* bytes
sh: echo: I/O error
passwd: Authentication token manipulation error
(chfn|groupadd|useradd): (cannot lock|failure while writing changes to) /etc/(group|gshadow|passwd|shadow|subuid)
(groupadd|useradd): (unable to lock|cannot rewrite) (group|password) file
INVOKE-RC.D: INITSCRIPT (MYSQL|POSTGRESQL|POSTGRESQL-8.3), ACTION "(RE)?START" FAILED.
invoke-rc.d: initscript (mysql|postgresql|postgresql-8.3), action "(re)?start" failed.
The PostgreSQL server failed to start.
No database found online on port 5432
unable to connect to postgresql server
Failed to connect to postgres.
PG::ConnectionBad: could not connect to server
psql: FATAL: password authentication failed for user
createuser: could not connect to database postgres: could not connect to server: No such file or directory
Non-default port in /etc/postgresql/.*/main/postgresql.conf
Firebird .* server already running.
^RuntimeError: maximum recursion depth exceeded while calling a Python object
^Traceback
^IndentationError:
^NameError:
^OSError:
^SyntaxError:
in failed logs.)
Please review the following logfiles/packages.
If it is always the same package failing, it's likely to be an issue in the
package.
The following logfiles have been deleted:
----------------------------------------------------------------------
/srv/piuparts.debian.org/master/jessie2Xstretch/fail/dms-core_None.log
The PostgreSQL server failed to start. Please check the log output:
invoke-rc.d: initscript postgresql, action "start" failed.
/srv/piuparts.debian.org/master/jessie2stretch/fail/dms-core_None.log
The PostgreSQL server failed to start. Please check the log output:
invoke-rc.d: initscript postgresql, action "start" failed.
/srv/piuparts.debian.org/master/sid/fail/libtomcat8.0-java_8.0.46-1.log
0m15.7s ERROR: Command failed (status=100): ['chroot', '/srv/piuparts.debian.org/tmp/tmp0ZVoe8', 'apt-cache', 'show', 'libtomcat8.0-java=8.0.46-1']
/srv/piuparts.debian.org/master/sid/fail/python3-lupa_1.5+dfsg-1.log
0m15.0s ERROR: Command failed (status=100): ['chroot', '/srv/piuparts.debian.org/tmp/tmpH7_YsQ', 'apt-cache', 'show', 'python3-lupa=1.5+dfsg-1']
More information about the Piuparts-reports
mailing list