forum.opsi.org

Hi,

Till just a couple of minutes ago Opsi worked well.
After some network problems and a reboot of Opsi i can't "execute now". Received error "no json object could be decoded".

When i run opsi-setup --init-current-config i receive at the end an error :

[3] [Mar 13 10:39:35] 'utf8' codec can't decode byte 0xe3 in position 0: invalid continuation byte (__init__.py|618)

Complete output :

[5] [Mar 13 10:39:33] Creating base path: '/var/lib/opsi/config' (File.py|233)
[5] [Mar 13 10:39:33] Try to find a Configserver. (opsi-setup|2665)
[5] [Mar 13 10:39:33] Getting current system config (opsi-setup|123)
[5] [Mar 13 10:39:33] System information: (opsi-setup|176)
[5] [Mar 13 10:39:33] distributor : Debian (opsi-setup|177)
[5] [Mar 13 10:39:33] distribution : Debian GNU/Linux 6.0.10 (squeeze) (opsi- setup|178)
[5] [Mar 13 10:39:33] ip address : 192.168.13.60 (opsi-setup|179)
[5] [Mar 13 10:39:33] netmask : 255.255.255.0 (opsi-setup|180)
[5] [Mar 13 10:39:33] subnet : 192.168.13.0 (opsi-setup|181)
[5] [Mar 13 10:39:33] broadcast : 192.168.13.255 (opsi-setup|182)
[5] [Mar 13 10:39:33] fqdn : opsi-nl-dev.dev.ict.nl (opsi-setup|183)
[5] [Mar 13 10:39:33] hostname : opsi-nl-dev (opsi-setup|184)
[5] [Mar 13 10:39:33] domain : dev.ict.nl (opsi-setup|185)
[5] [Mar 13 10:39:33] win domain : ICT (opsi-setup|186)
[5] [Mar 13 10:39:33] Configuring client user pcpatch (opsi-setup|484)
[5] [Mar 13 10:39:33] Creating RSA private key for user pcpatch in '/var/lib/ opsi/.ssh/id_rsa' (opsi-setup|498)
[5] [Mar 13 10:39:34] Setting rights (opsi-setup|548)
[5] [Mar 13 10:39:34] Setting rights on directory '/var/lib/opsi/.ssh' (opsi-set up|635)
[3] [Mar 13 10:39:35] 'utf8' codec can't decode byte 0xe3 in position 0: invalid continuation byte (__init__.py|618)

When i run opsi-setup --configure-mysql i see this error :

[2] [Mar 13 10:55:47] Traceback: (Logger.py|767)
[2] [Mar 13 10:55:47] line 3054 in '<module>' in file '/usr/bin/opsi-setup' (Logger.py|767)
[2] [Mar 13 10:55:47] line 3006 in 'main' in file '/usr/bin/opsi-setup' (Logger.py|767)
[2] [Mar 13 10:55:47] line 2266 in 'configureMySQLBackend' in file '/usr/bin/opsi-setup' (Logger.py|767)
[2] [Mar 13 10:55:47] line 165 in 'configureMySQLBackend' in file '/usr/lib/python2.6/dist-packages/OPSI/Util/Task/ConfigureBackend/MySQL.py' (Logger.py|76 7)
[2] [Mar 13 10:55:47] line 397 in 'backend_createBase' in file '/usr/lib/py thon2.6/dist-packages/OPSI/Backend/SQL.py' (Logger.py|767)
[2] [Mar 13 10:55:47] line 435 in 'getTables' in file '/usr/lib/python2.6/d ist-packages/OPSI/Backend/MySQL.py' (Logger.py|767)
[2] [Mar 13 10:55:47] line 221 in 'getSet' in file '/usr/lib/python2.6/dist -packages/OPSI/Backend/MySQL.py' (Logger.py|767)
[2] [Mar 13 10:55:47] line 419 in 'execute' in file '/usr/lib/python2.6/dis t-packages/OPSI/Backend/MySQL.py' (Logger.py|767)
[2] [Mar 13 10:55:47] line 166 in 'execute' in file '/usr/lib/pymodules/pyt hon2.6/MySQLdb/cursors.py' (Logger.py|767)
[2] [Mar 13 10:55:47] line 35 in 'defaulterrorhandler' in file '/usr/lib/py modules/python2.6/MySQLdb/connections.py' (Logger.py|767)
[2] [Mar 13 10:55:47] ==>>> (1, "Can't create/write to file '/tmp/#sql_851_ 0.MYI' (Errcode: 13)") (opsi-setup|3058)

ERROR: (1, "Can't create/write to file '/tmp/#sql_851_0.MYI' (Errcode: 13)")




Any ideas what went wrong?

Thanks in advance,

Kees....

[2] [Mar 13 10:55:47] ==>>> (1, "Can't create/write to file '/tmp/#sql_851_ 0.MYI' (Errcode: 13)") (opsi-setup|3058)

Permissions on /tmp/?

Hi,

Thanks for replying.

Nope, permissions are okay

Greetings...

Hello Kees,

loggenk hat geschrieben:When i run opsi-setup --init-current-config i receive at the end an error :

[3] [Mar 13 10:39:35] 'utf8' codec can't decode byte 0xe3 in position 0: invalid continuation byte (__init__.py|618)

I've seen this before. Usually this was done by re-running the command and then it would not appear again.

Does re-running the command 1-3 times fix this problem?


With kind regards

Niko

Hi Niko,

I'm afraid its also not working.

Rebooted number of times, re-runned the command couple of times

Greetings,

Kees..

Hi,

This morning I tried to run opsi-setup --init-current-config, i received the following error:

root@opsi-nl-dev:~# opsi-setup --init-curent-config

Usage: opsi-setup [options]

Options:
-h, --help show this help
-l log-level 0..9

--log-file <path> path to log file
--backend-config <json hash> overwrite backend config hash values
--ip-address <ip> force to this ip address (do not lookup by name )
--register-depot register depot at config server
--set-rights [path] set default rights on opsi files (in [path] onl y)
--init-current-config init current backend configuration
--update-from=<version> update from opsi version <version>
--update-mysql update mysql backend
--update-ldap update ldap backend
--update-univention update univention backend
--update-file update file backend
--configure-mysql configure mysql backend
--edit-config-defaults edit global config defaults
--cleanup-backend cleanup backend
--auto-configure-samba patch smb.conf
--auto-configure-dhcpd patch dhcpd.conf
--renew-opsiconfd-cert renew opsiconfd-cert
--patch-sudoers-file patching sudoers file for tasks in opsiadmin co ntext.

[2] [Mar 16 07:20:30] Traceback: (Logger.py|767)
[2] [Mar 16 07:20:30] line 3054 in '<module>' in file '/usr/bin/opsi-setup' (Logger.py|767)
[2] [Mar 16 07:20:30] line 2907 in 'main' in file '/usr/bin/opsi-setup' (Lo gger.py|767)
[2] [Mar 16 07:20:30] line 89 in 'getopt' in file '/usr/lib/python2.6/getop t.py' (Logger.py|767)
[2] [Mar 16 07:20:30] line 153 in 'do_longs' in file '/usr/lib/python2.6/ge topt.py' (Logger.py|767)
[2] [Mar 16 07:20:30] line 170 in 'long_has_args' in file '/usr/lib/python2 .6/getopt.py' (Logger.py|767)
[2] [Mar 16 07:20:30] ==>>> option --init-curent-config not recognized (ops i-setup|3058)

ERROR: option --init-curent-config not recognized

loggenk hat geschrieben:ERROR: option --init-curent-config not recognized

It's "current", not "curent".

Regards


Holger

Hi Holger,

Stupid of me!

I found out that one of my problems were because of a full harddisk.
Corrected this problem.

Still i get the mysql error about not wirite to /tmp

Hi loggenk,

have you special characters in your mysql-user-credentials for opsi?

No I haven't.

System worked correctly for about 1.5 year now.
Problems occured after a network crash.