[Solved]Glassfish's updatetool

Question

Hello,
I can't run updatetool, because I am missing some 32 bit libraries, but IDK what libraries I'm exactly missing. Could anyone help?
[cybuch@MedeiS bin]$ sh updatetool
WX import error. Verify the WX widgets are in the PYTHONPATH.
The following can be reported to GlassFish Update Tool 2.3.5 Development Team <[email protected]>.
Traceback (innermost last):
File "/home/cybuch/glassfish/updatetool/vendor-packages/updatetool/common/boot.py", line 283, in init_app_locale
import wx
File "wx/__init__.py", line 45, in ?
File "wx/_core.py", line 4, in ?
ImportError: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory
There was an error running
/home/cybuch/glassfish/updatetool/bin/../../pkg/python2.4-minimal/bin/python
You are running on a 64 bit Linux distribution and the 32 bit Linux
compatibility libraries do not appear to be installed. In order to use
the Update Center tools you must install the 32 bit compatibility libraries.
On Ubuntu (and possibly other Debian based systems) please install the
ia32-libs package. On RedHat 4 (and other RPM based systems), you may
need to add multiple 'compat' runtime library packages. Please see the
Update Center Release Notes for more information
Solution:
Install every package from ImportError. There will be one package that's missing, I've forgotten which one is it, but google about it - you'll have to create a symlink to analogic package.
Last edited by cybuch (2012-10-02 20:00:06)

Answer 1

In my case I also use
RuntimeMaxUse=50M
However my file sizes do seem approximately in step with what is expected from du -sh
$ sudo journalctl --disk-usage
Journals take up 768.0K on disk.
$ du -sh /var/log/journal
780K /var/log/journal
Mind you I recently removed the journal directory to clean out coredumps by stopping the systemd-journald service and then doing the following before rebooting
# rm -fr /var/log/journal
# mkdir /var/log/journal
The files look sensible since doing that.  I have had the journal files corrupted at various times when there has been a system hang and this is easily seen if the journal is verified with
# journalctl --verify
Unless the above shows pass on all files I remove the journal directory entirely to clean it up as I believe that systemd can't clean up corrupted binary journal files.
Maybe the journal disk usage excludes things like coredumps?
Last edited by mcloaked (2013-11-04 19:50:43)