Previous Znuny Deployment mysteriously pending...

[tupson]

Greetings,

It would appear at some point early on a previous upgrade of Znuny failed (v6.0.33-2) and wasn't successfully cleared. However, since then we have successfully upgraded to v6.2.2 and ran all necessary migration scripts, database rebuilds, etc -- and the Help Desk Tool is working as intended.

However, whenever I run an apt-get update/upgrade - the following Znuny script loops and fails:

How can I purge this so it does not continue to be bothersome? We are running Ubuntu 20.04.3 LTS

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.01.03 17:17:20 =~=~=~=~=~=~=~=~=~=~=~=

The following packages were automatically installed and are no longer required:
apt-show-versions libapt-pkg-perl
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.

Setting up znuny (6.0.33-2) ...

chown: invalid group: ‘otrs:apache’
chown: invalid group: ‘otrs:apache’
chown: invalid group: ‘otrs:apache’

chmod: cannot access '/opt/otrs/Kernel/System/Console/Command/Dev/Tools/Migrate': No such file or directory

chmod: cannot access '/opt/otrs/scripts/DBUpdateTo6': No such file or directory

chmod: cannot access '/opt/otrs/scripts/DBUpdateTo6/TaskConfig': No such file or directory

chmod: cannot access '/opt/otrs/scripts/DBUpdateTo6/UpgradeDatabaseStructure': No such file or directory

chmod: cannot access '/opt/otrs/scripts/test/Console/Command/Dev/Tools/Migrate': No such file or directory

chmod: cannot access '/opt/otrs/scripts/test/Console/Command/Maint/OTRSBusiness': No such file or directory

chmod: cannot access '/opt/otrs/scripts/test/DBUpdate': No such file or directory

chown: invalid group: ‘otrs:apache’
chown: invalid group: ‘otrs:apache’
chown: invalid group: ‘otrs:apache’

dpkg: error processing package znuny (--configure):
installed znuny package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:
znuny

E: Sub-process /usr/bin/dpkg returned an error code (1)

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.01.03 17:17:20 =~=~=~=~=~=~=~=~=~=~=~=

[tupson]

^ bump. Anyone have any idea how to clear legacy installer scripts that are no longer needed?

[root]

Hi,

Since this is seems to be triggered by the package provided by Debian you should ask the package maintainer of the Debian project.

- Roy

[tupson]

Hi,

Since this is seems to be triggered by the package provided by Debian you should ask the package maintainer of the Debian project.

- Roy

Do you know who and where I should go to ask/inquire?

[tupson]

Hi,
Since this is seems to be triggered by the package provided by Debian you should ask the package maintainer of the Debian project.
- Roy

Actually, I believe you read the log wrong. The log errors all result to a "Znuny" installation. (See bold text below)

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.01.03 17:17:20 =~=~=~=~=~=~=~=~=~=~=~=

Setting up znuny (6.0.33-2) ...

dpkg: error processing package znuny (--configure):
installed znuny package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:
znuny

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.01.03 17:17:20 =~=~=~=~=~=~=~=~=~=~=~=

I even went to the Znuny download page and matched the installation files previously used:

https://download.znuny.org/releases/znuny-6.0.33.tar.gz

So I believe I am in the right location.

[root]

So I believe I am in the right location.

Hi,

There is nothing to believe, it's just a fact. Since there is no debian package provided by Znuny and none of the archives (.tar.gz, .zip, etc.) calls a script by itself.
Executing a script is done by package manager like RPM or dpkg. And even the RPM packages we provide does not execute the migration script.

The missing directory like /opt/otrs/scripts/DBUpdateTo6/UpgradeDatabaseStructure moved to another location in the debian package. See https://packages.debian.org/bullseye/all/otrs2/filelist

For more details check the package site at https://packages.debian.org/bullseye/otrs2

Maybe someone tried to convert the RPM with alien, this could be the reason why the wrong user/group is user. Usually the group apache is used by RHEL base setups, for Debian/Ubuntu based it's www-data

- Roy

[tupson]

So I believe I am in the right location.

Maybe someone tried to convert the RPM with alien, this could be the reason why the wrong user/group is user. Usually the group apache is used by RHEL base setups, for Debian/Ubuntu based it's www-data

- Roy

Thanks for the follow up, I still don't get why its indicating an installation of "Znuny" if its not a 'Znuny' installer/script. It would make sense if it were writing out "OTRS installer failures/errors" but its pretty evident it is mentioning Znuny throughout the error log.

But I cannot argue what I don't know... Since the OTRS Community Forum migrated to a Znuny Community; be it I assume they stopped building a community OTRS package, where would I now go to ask for support on this specifically? I cannot find where you are asking me to take my question.

[jojo]

just try it here: https://bugs.debian.org/cgi-bin/pkgrepo ... t=unstable

(Using the Debian packages was always a pain)

[tupson]

I found out what was causing the issue.

There was a file called: znuny.postinst found in the /var/lib/dpkg/info/ directory.

There was also three additional files ( znuny.conffiles, znuny.list and znuny.md5sums ) in this same path. As soon as I removed these files from that directory, the error stopped.



This folder definitely refers to Debian packages - but why would Znuny files be within a Debian package?

[root]

This folder definitely refers to Debian packages - but why would Znuny files be within a Debian package?

Because they are part of the package otrs2 (which is a Znuny)?

- Roy

[tupson]

Executing a script is done by package manager like RPM or dpkg. And even the RPM packages we provide does not execute the migration script.

- Roy

I took that to mean there shouldn't be any Znuny files within the Debian packages and this error was directly with non-Znuny deployment(s). At any rate, I took your recommendation to ask a Debian POC.

The Debian POC (Patrick) responded with the following:

----------------------------------------------------
Patrick Matthäi <patrick@linux-dev.org>
3:24 AM (5 hours ago)

Hi,

Sorry, this is not a problem of the znuny/otrs2 package in Debian, this does not come from us, also Ubuntu is not Debian.

Debian and the Debian otrs2/znuny packages are working and they are maintained. Ubuntu is not maintaining this package and there is also no znuny package with scripts.

So it would be nice to clarify this is false information from the Znuny forum.
----------------------------------------------------

It appears neither party wants to claim this situation as it being an issue with their packages/scripts (giggles) -- but I dug into all location(s) that referenced 'Znuny*' via WinSCP and found the sources of the problem as indicated earlier; thus, I will resume this matter as closed. Appreciate all of the information on the differences within the packages; to help understand this for any future issues that may arise.

[root]

Hi,

Once again: The files you've found in /var/lib/dpkg/info/ znuny.* belong to a deb package. If they are not part of the official Debian/Ubuntu package you should ask the person who's maintaining your Ubuntu server. Znuny does not provide deb packages and we do not have any of these file included. See also https://www.debian.org/doc/manuals/debi ... intscripts where you can read that these files belong to .deb packages.

- Roy

[tupson]

Hi,

Once again: The files you've found in /var/lib/dpkg/info/ znuny.* belong to a deb package. If they are not part of the official Debian/Ubuntu package you should ask the person who's maintaining your Ubuntu server. Znuny does not provide deb packages and we do not have any of these file included. See also https://www.debian.org/doc/manuals/debi ... intscripts where you can read that these files belong to .deb packages.

- Roy

I am the owner and installer of our OTRS. So this is just a mystery to all of us. Oh well.