search

perfsonar / project

The perfSONAR project's primary wiki and issue tracker.
Apache License 2.0
54 stars 10 forks source link

MA and LS registration config files being replaced with binary files #765

Closed arlake228 closed 9 years ago

arlake228 commented 9 years ago

Original issue 766 created by arlake228 on 2013-09-04T13:55:09.000Z:

It's been reported that in a few instances upgrading to 3.3.1 replaced the perfsonarbupy_ma, traceoute ma, and ls registraion daemon.pl files with binary garbage. I've had trouble recreating this so far. Here are the steps followed by the user that lead to this situation:

From the user:

Hi Andy, these are all the steps from the start:

1) Installation of 3.3 from scratch (NetInstall, 64-bit), using the migration script, on both servers

2) Various patching of the OWAMP/PingEr server

up to this moment, all working

3) yum update of both servers

4) after the reboot of both servers, the Administrative Information and Community information disappeared; all the MAs on both servers were in "non running" state

5) I set manually the Administrative Info and Community, on both servers; tried to reboot, but the MAs still not running

6) tried to issue: /etc/init.d/discover_external_address restart and /opt/perfsonar_ps/toolkit/scripts/service_watcher --regular_restart but they returned the errors I pointed in a previous email in the thread

7) tried other reboots, but to no avail.

I've tried a complete fsck and the filesystems seems ok, and what's more the exact same things happened on both servers (I've checked the various .conf file and they are in the same state on the other server), so I'd exclude hardware-related problems.

Cheers.

arlake228 commented 9 years ago

Comment #1 originally posted by arlake228 on 2013-10-14T13:18:17.000Z:

This was specific to a non-standard update we had a few people do to try some beta version of the mesh config. It has been resolved for those users so closing issue.