Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfSONAR won't save settings

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfSONAR won't save settings


Chronological Thread 
  • From: Chris Griffin <>
  • To: Oleg Moiseichuk <>,
  • Subject: Re: [perfsonar-user] perfSONAR won't save settings
  • Date: Wed, 16 May 2018 17:05:06 -0400
  • Ironport-phdr: 9a23:t4DZLBXLl58Zhf/vu2Pv83T8z67V8LGtZVwlr6E/grcLSJyIuqrYbBaOt8tkgFKBZ4jH8fUM07OQ7/i7HzRYqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjWwba98IRmssQndqtQdjJd/JKo21hbHuGZDdf5MxWNvK1KTnhL86dm18ZV+7SleuO8v+tBZX6nicKs2UbJXDDI9M2Ao/8LrrgXMTRGO5nQHTGoblAdDDhXf4xH7WpfxtTb6tvZ41SKHM8D6Uaw4VDK/5KpwVhTmlDkIOCI48GHPi8x/kqRboA66pxdix4LYeZyZOOZicq/Ye94RWGhPUdtLVyFZH42ycYUPAeoCM+hWoYbyqFkBogexCwS3GOPiyCVFimPq0aA00eksFxzN0gw6H9IJtXTZtMv4NKcIUeC016nD0DTNb+lX2Tfz5ojIcxYhquyLUL1sfsrR00gvFw3LjlWRr4zoJD2V1uAXs2id8eVgSfiji2k9qwF+uzWiwNonhIrRho8Ny13J+j91zYY0KNGiTEN2YcSoHZVRui2CKod6XMAvT3t2tCokyLAKo4C3cDUUxJg9wxPSavqKeJWS7B35TuaeOzJ4iWpleL2hgxay9lCtyuv7VsaoyVpKtTRKksPStnwUyRDf8M6HSvxh8Uu71zaP0xrT6udaLkAoj6bbLIQhwrEompoSt0TMADP2lV33gaKZbEkp+uml5/7jb7jmvJOROY55hhn7Mqs0m8y/Beo4MhIJX2ie4emzyLLj/Vf4QLVEgP02k6/ZvYvUJcQfvK65BRFa0po55xa4FTem38wUnWMbI1JdZBKHk4/pNknWIP/mF/e/jU+skDBtx//cJL3tG4jNLmPdn7f7Zrt9709cyBEvzdBE+Z5YELABIPTvWkDvrtzYCAE2MxCqz+r9Ftpyy54eCiqzBfq+NK7d+XqP5/kiIuKMeYxd7DH4A/Is/PjjkTkziAlZNbGkx5UMb3axBLF7OEiDSXvqntobF2oW5EwzQPG5pkeFVGt4Z2yzROoT/DA1BoOgRdPISZqsjrKA2g+1GodQa3wADUqDRyS7P76YUusBPXrBavRqlSYJAP34E9cs

I have just recently run into the same issue, although my symptoms were different.
Upon saving I got "Error - Couldn't save Regular Testing configuration", but
no errors in web_admin.log. Tracked it to the same issue. I am not sure if this is
the best way to correct it, but try this:

* edit /etc/perfsonar/toolkit/configdaemon.conf
* change the "address localhost" to "address localhost4"
* restart the perfsonar-configdaemon.service

This seemed to start happening to us after a recent sent of patching and
reboot activity.

Tnx
Chris

On 05/16/2018 09:11 AM, Oleg Moiseichuk wrote:
Hello.

Would you please help me with advice.

I created several perfSONAR nodes on the base of Gigabyte BRIX 3160.
Firstly I performed installation (from perfSONAR full ISO version 4.0.2) on
one node, then I cloned this node with Clonezilla and set proper IP addresses
on all 4 nodes.
N.B. I also changed interface name from enp3s0 to eth0, if this is relevant.

I placed all the nodes on the desired spots and then I found out that I cannot change
any settings. I tried changing location, system name, NTP server settings. When I alter
some setting using web admin and press "Save" button, it reverts to old
settings.

I found several errors in the log of webadmin. They look as the possible
cause of my problem:

/var/log/perfsonar/web_admin/web_admin.log:2018/05/16 12:17:53 (9096) ERROR>
ConfigClient.pm:93
perfSONAR_PS::NPToolkit::ConfigManager::ConfigClient::saveFile - Problem writing
file /etc/ntp.conf: RPC::XML::Client::simple_request:
RPC::XML::Client::send_request: HTTP server error: Can't connect to
127.0.0.1:9000 (Connection refused)

/var/log/perfsonar/web_admin/web_admin.log:2018/05/16 13:06:39 (12934) ERROR>
ConfigClient.pm:93
perfSONAR_PS::NPToolkit::ConfigManager::ConfigClient::saveFile - Problem writing
file /etc/perfsonar/lsregistrationdaemon.conf: RPC::XML::Client::simple_request:
RPC::XML::Client::send_request: HTTP server error: Can't connect to
127.0.0.1:9000 (Connection refused)

I noticed also one thing:
------------------------
# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 127.0.0.1:37469 0.0.0.0:* LISTEN
10552/java
tcp 0 0 127.0.0.1:7199 0.0.0.0:* LISTEN
10552/java
tcp 0 0 0.0.0.0:9922 0.0.0.0:* LISTEN
1132/sshd
tcp 0 0 127.0.0.1:9160 0.0.0.0:* LISTEN
10552/java
tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN
1127/memcached
tcp 0 0 127.0.0.1:9042 0.0.0.0:* LISTEN
10552/java
tcp 0 0 127.0.0.1:7000 0.0.0.0:* LISTEN
10552/java
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN
1186/postgres
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
1828/master
tcp6 0 0 :::861 :::* LISTEN
1138/owampd
tcp6 0 0 :::9922 :::* LISTEN
1132/sshd
tcp6 0 0 ::1:9000 :::* LISTEN
1961/toolkit_config
tcp6 0 0 ::1:11211 :::* LISTEN
1127/memcached
tcp6 0 0 :::80 :::* LISTEN
1133/httpd
tcp6 0 0 :::4823 :::* LISTEN
1226/bwctld
tcp6 0 0 ::1:5432 :::* LISTEN
1186/postgres
tcp6 0 0 ::1:25 :::* LISTEN
1828/master
tcp6 0 0 :::443 :::* LISTEN
1133/httpd
udp 0 0 127.0.0.1:11211 0.0.0.0:*
1127/memcached
udp 0 0 80.94.170.182:123 0.0.0.0:*
747/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:*
747/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:*
747/ntpd
udp6 0 0 ::1:11211 :::*
1127/memcached
udp6 0 0 fe80::e2d5:5eff:fe1:123 :::*
747/ntpd
udp6 0 0 ::1:123 :::*
747/ntpd
udp6 0 0 :::123 :::*
747/ntpd
------------------------
toolkit_config_daemon is running, but it listens only on ::1:9000, no sign of
opened port for IPv4.
I've got one more perfSONAR host and 'netstat -tulpn' shows 127.0.0.1:9000 in
its output.

How this issue can be fixed?


--
Chris Griffin

Chief Network Architect Phone: (352) 273-1051
Florida LambdaRail Fax: (352) 392-9440
University of Florida/FLR Gainesville, FL 32611



Archive powered by MHonArc 2.6.19.

Top of Page