Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
--
I noticed this started happening after upgrade yesterday. 06/16/2015. So i manually deleted all the iptables. Purged out the install, manually erased every conf file directory in ~/.confg and /etc/pgl, erased all log directories, re-installed, and it worked.. upon restart this happens above. I look in /var/lib/pgl/ and there is a .pglcmd.iptables.remove.sh.tmp. I copied that over to the given file name in the directory and it just deletes it upon restart.
2015-06-17 12:20:46 EDT Begin: pglcmd restart
Stopping pglcmd.wd^M^[[144G[ OK ]
Deleting iptables ...
Iptables deleted.
Stopping pgld^M^[[144G[ OK ]
Inserting iptables ...
..Setting up iptables for INPUT:
....Creating chainiptables: Chain already exists.
^M^[[144G[^[[31mfail^[[39;49m]
cat: /var/lib/pgl/.pglcmd.iptables.remove.sh: No such file or directory
Deleting iptables ...
Iptables deleted.
2015-06-17 12:21:03 EDT Begin: pglcmd force-restart
Stopping pglcmd.wd^M^[[144G[ OK ]
Deleting iptables ...
Iptables deleted.
Stopping pgld^M^[[144G[ OK ]
Building blocklist ...
WARN: No valid ASCII blocklist format line:
INFO: ASCII: 884179 entries loaded from "STDIN"
INFO: Merged 484418 of 884179 entries.
INFO: Blocking 399761 IP ranges (1591157561 IPs).
Blocklist built.
Inserting iptables ...
..Setting up iptables for INPUT:
....Creating chainiptables: Chain already exists.
^M^[[144G[^[[31mfail^[[39;49m]
cat: /var/lib/pgl/.pglcmd.iptables.remove.sh: No such file or directory
Deleting iptables ...
Iptables deleted.
2015-06-17 12:28:54 EDT Begin: pglcmd stop_quick
Stopping pglcmd.wd * Stopping PeerGuardian Linux pgld
^M^[[%i%p1%dG[ OK ]
Deleting iptables ...
Iptables deleted.
Stopping pgld ...done.
2015-06-17 12:28:54 EDT End: pglcmd stop_quick
2015-06-17 12:29:45 EDT Begin: pglcmd start
Inserting iptables ...
..Setting up iptables for INPUT:
....Creating chainiptables: Chain already exists.
* Starting PeerGuardian Linux pgld
^M^[[%i%p1%dG[^[[31mfail^[[39;49m]
cat: /var/lib/pgl/.pglcmd.iptables.remove.sh: No such file or directory
Deleting iptables ...
Iptables deleted.
Hi,
thanks for reporting that. I heard of this just yesterday from someone else. I've pushed some changes to the git repository that might fix that.
The file /var/lib/pgl/.pglcmd.iptables.remove.sh is created generically on every pglcmd start, and removed on stop again. I moved the creation of that file a bit earlier, to hopefully correct the current problems. But it seems they aren't permanent, but end as soon as the iptables have been cleaned once.
Can you tell me, which updates you got, that might have caused this (something related to iptables, net* or the kernel itself)?
Greets
jre
I think it was the apparmor, if I remember and a few others, I do not know how to check dates of when the last update occurred. I could compare the the dates when this was submitted to a -5 days before. If there is a file that has date of last update somewhere I would be able to look at that. Possibly if I remember on the apt file stored somewhere with all the details of package name, date, name, files, etc, somewhere If I remember.
If a package fails to install you have to edit this file and erase the multi-line entry for the file and "apt-get get update" again.
Last edit: Vincent B 2015-06-25
It was /var/lib/dpkg/status and it does not show install date as i thought it did. just package info and status.
invoke-rc.d: initscript pgl, action "start" failed.
dpkg: error processing package pglcmd (--configure):
subprocess installed post-installation script returned error exit status 8
dpkg: dependency problems prevent configuration of pglgui:
pglgui depends on pglcmd (>= 2.3.0-1~trusty); however:
Package pglcmd is not configured yet.
pglgui depends on pglcmd (<< 2.3.0-1~trusty.1~); however:
Package pglcmd is not configured yet.
dpkg: error processing package pglgui (--configure):
dependency problems - leaving unconfigured
Setting up libpython3.4-minimal:amd64 (3.4.0-2ubuntu1.1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
Setting up libpython3.4-stdlib:amd64 (3.4.0- 2ubuntu1.1) ...
Setting up libpython3.4:amd64 (3.4.0-2ubuntu1.1) ...
Setting up python3.4-minimal (3.4.0-2ubuntu1.1) ...
Setting up python3.4 (3.4.0-2ubuntu1.1) ...
Setting up libpython2.7-minimal:amd64 (2.7.6-8ubuntu0.2) ...
Setting up python2.7-minimal (2.7.6-8ubuntu0.2) ...
Setting up libpython2.7-stdlib:amd64 (2.7.6-8ubuntu0.2) ...
Setting up python2.7 (2.7.6-8ubuntu0.2) ...
Setting up libpython2.7:amd64 (2.7.6-8ubuntu0.2) ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
Processing triggers for menu (2.1.46ubuntu1) ...
Errors were encountered while processing:
pglcmd
pglgui
E: Sub-process /usr/bin/dpkg returned an error code (1)
vincent@Server:~$ sudo dpkg-reconfigure --force pglcmd
* Stopping PeerGuardian Linux pgld [ OK ]
pgld will soon be started ...
If any blocklists are missing, they will be downloaded. This may take several
minutes. Please be patient and don't abort. If you want to follow the update
process, then do in another terminal a
tail -f /var/log/pgl/pglcmd.log
The lists are saved to /var/spool/pgl/.
The installation of pglcmd will fail, if starting pgld fails. So if
downloading the blocklists fails temporarily, the installation will fail. In
this case you may turn the automatic starting off by setting in
/etc/pgl/pglcmd.conf:
INIT="0"
Then complete the installation and turn the automatic start on again:
sudo dpkg-reconfigure --force pglcmd
Please be patient ...
* Starting PeerGuardian Linux pgld [fail]
invoke-rc.d: initscript pgl, action "start" failed.
after performing a update;upgrade;dist-upgrade
pgl 2.3.1 with the mentioned fix was released on 2015-11-17.