package aiccu 20070115-15.1ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[David Seppi]

I couldn't install the packet aiccu.
I was aked about my favoured broker and my credentials. After that I got this error message:

aiccu (20070115-15.1ubuntu1) wird eingerichtet ...
start: Job failed to start
invoke-rc.d: initscript aiccu, action "start" failed.
dpkg: Fehler beim Bearbeiten von aiccu (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Trigger für ureadahead werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 aiccu
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: aiccu 20070115-15.1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
AptOrdering:
 aiccu: Install
 aiccu: Configure
Architecture: amd64
Date: Mon Mar 3 20:25:13 2014
DpkgHistoryLog:
 Start-Date: 2014-03-03 20:24:56
 Commandline: apt-get install aiccu
 Install: aiccu:amd64 (20070115-15.1ubuntu1)
DuplicateSignature: package:aiccu:20070115-15.1ubuntu1:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2013-08-29 (185 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130626)
MarkForUpload: True
SourcePackage: aiccu
Title: package aiccu 20070115-15.1ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.aiccu.conf: [modified]
mtime.conffile..etc.aiccu.conf: 2014-03-03T20:25:12.518354
var.log.aiccu.log:
 20140303 20:25:12 Starting SixXS Automatic IPv6 Connectivity Client Utility
 20140303 20:25:12 Checking access to tic.sixxs.net:
 20140303 20:25:12 OK
 20140303 20:25:12 Command line: /usr/sbin/aiccu start
 20140303 20:25:13 Stopping SixXS Automatic IPv6 Connectivity Client Utility

[Jeroen Massar (massar)]

Without the output of aiccu or the script that is calling it, there is little to say as except for the line that says that the post-install script failed, there is no actual error message.

You might want to check /var/log/* for aiccu related messages; and/or try 'dpkg --configure aiccu' and/or try starting aiccu manually.

[David Seppi (dseppi)]

Ok, it's no bug, it's just too little information.

/var/log/syslog told me that "TIC Server is currently not available". It was just a misconfiguration at server site, the aiccu package seems to be ok.
I could solve that, but I expected such informations in /var/log/aiccu.log or as error message on stderr. ("dpkg --reconfigure aiccu" or "/etc/init.d/aiccu restart" are not verbous at all).

Thanks for your help!

[Jeroen Massar (massar)]

> /var/log/syslog told me that "TIC Server is currently not available".

There is likely another error above that message, as that is just the general marker.

> It was just a misconfiguration at server site,

What kind of misconfiguration? How did you resolve that misconfiguration?

> I could solve that, but I expected such informations in /var/log/aiccu.log or
> as error message on stderr. ("dpkg --reconfigure aiccu" or "/etc/init.d/aiccu restart" are not verbous at all).

Unless there is something special creating and filling in a /var/log/aiccu.log, I don't expect that to exist.

AICCU logs to syslog in daemonized mode and to stderr in non-daemonized mode.

[David Seppi (dseppi)]

> There is likely another error above that message, as that is just the general marker.

Hm, there's just another error below that message.

| Mar 3 20:37:28 david aiccu[6866]: TIC Server is currently not available
| Mar 3 20:37:28 david aiccu[6866]: Couldn't retrieve first tunnel for the above reason, aborting

> What kind of misconfiguration? How did you resolve that misconfiguration?

The tunnel wasn't assigned to my handle yet. My tunnel request had to be confirmed by the tunnel broker.

> Unless there is something special creating and filling in a /var/log/aiccu.log, I don't expect that to exist.
>
> AICCU logs to syslog in daemonized mode and to stderr in non-daemonized mode.

That's strange. I installed aiccu with "apt-get install aiccu" and didn't change its configuration, I just entered my account data.
I still get new entries in /var/log/aiccu.log at startup time.