| March 18, 2013 10:12 |
Installation Fails On SUSE Linux SLES10 SP4
#226190
|
|
|
Reply with Quote | Quick Reply | Top
|
Dave Howland

Novice
Join Date: 18.3.2013
Posts: 4
|
Installing avg2013flx-r3115-a6155.i386.rpm on Suse Linux Enterprise Server 10 SP4 fails with a floating point exception error. This is the output from the installation:
$ sudo rpm -i avg2013flx-r3115-a6155.i386.rpm
Installing 'avgd' service initscripts...
Registering 'avgd' service to runlevels...
avgd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Please do configuration with /opt/avg/av/bin/avgsetup
Generating unique user id
/var/tmp/rpm-tmp.47850: line 57: 32174 Floating point exceptionavgdiag --gen-uid
Starting AVG AV
Starting avgd/opt/avg/av/etc/init.d/functions.common: line 159: 32194 Floating point exception$nice "$AVG_DIAG" --fixcfg >/dev/null 2>&1
/opt/avg/av/etc/init.d/functions.common: line 159: 32195 Floating point exception$nice "$AVG_CTL" --start >/dev/null 2>&1
failed
error: %post(avg2013flx-r3115-a6155.i386) scriptlet failed, exit status 150
$
... and if I try to run any of the programs, e.g. avgupdate, I get the same error:
$ sudo avgupdate
Floating point exception
$
Any ideas?
Dave.
|
| March 18, 2013 11:47 |
Re: Installation Fails On SUSE Linux SLES10 SP4
#226191
|
|
|
Reply with Quote | Quick Reply | Top
|
Dave Howland

Novice
Join Date: 18.3.2013
Posts: 4
|
Update - checking logs of existing servers that were working fine, the problem started following an update on the morning of 16th March. The log shows:
Sat Mar 16 03:10:01 GMT 2013: Performing Update
AVG command line update
Copyright (c) 2012 AVG Technologies CZ
Running update.
Failed to initialize configuration.
Operation failed with error number: 2
Then any subsequent operation has the "floating point exception" error.
|
| March 20, 2013 08:35 |
Re: Installation Fails On SUSE Linux SLES10 SP4
#226318
|
|
|
Reply with Quote | Quick Reply | Top
|
Dave Howland

Novice
Join Date: 18.3.2013
Posts: 4
|
Thanks for responding. This is the OS architecture:
$ uname -a
Linux betty 2.6.16.60-0.99.1-bigsmp #1 SMP Fri Oct 12 14:24:23 UTC 2012 i686 i686 i386 GNU/Linux
$
avgdiag doesn't run - it also has the floating point exception:
$ sudo avgdiag -c /home/chdave/diagcfg.xml
Floating point exception
$
There is nothing in /opt/avg/av/log.
Dave.
|
| March 20, 2013 12:09 |
Re: Installation Fails On SUSE Linux SLES10 SP4
#226332
|
|
|
Reply with Quote | Quick Reply | Top
|
JArda2

Moderator
Join Date: 2.7.2009
Posts: 43
|
Dave Howland wrote Update - checking logs of existing servers that were working fine, the problem started following an update on the morning of 16th March. The log shows:
Sat Mar 16 03:10:01 GMT 2013: Performing Update
AVG command line update
Copyright (c) 2012 AVG Technologies CZ
Running update.
Failed to initialize configuration.
Operation failed with error number: 2
Then any subsequent operation has the "floating point exception" error.
Can you please try to rename /opt/avg/av/lib/libgcc_s.so.1 to libgcc_s.so.1_off? Like this e.g.:
mv /opt/avg/av/lib/libgcc_s.so.1 /opt/avg/av/lib/libgcc_s.so.1_off
And try to run avgctl --start. Does it work?
Regards,
JArda
|
| March 25, 2013 14:04 |
Disapproved post
#226641
|
|
|
|
JArda2

Moderator
Join Date: 2.7.2009
Posts: 43
|
The post has been evaluated as inappropriate and therefore it was disapproved.
|
| March 25, 2013 14:04 |
Disapproved post
#226642
|
|
|
|
JArda2

Moderator
Join Date: 2.7.2009
Posts: 43
|
The post has been evaluated as inappropriate and therefore it was disapproved.
|
| March 25, 2013 14:04 |
Disapproved post
#226643
|
|
|
|
JArda2

Moderator
Join Date: 2.7.2009
Posts: 43
|
The post has been evaluated as inappropriate and therefore it was disapproved.
|
| March 25, 2013 14:04 |
Re: Installation Fails On SUSE Linux SLES10 SP4
#226644
|
|
|
Reply with Quote | Quick Reply | Top
|
JArda2

Moderator
Join Date: 2.7.2009
Posts: 43
|
Dave Howland wrote Yes, that now works. The daemon starts and I can run avgupdate.
Should I use this as a work-around? Will the problen re-occur folling a future update?
Thanks,
Dave.
Yes, this is workaround. And it should not re-occur since we do not put libgcc_so.1 into update.
I am glad it helped.
Regards,
JArda
|