Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] problems writing to central MA using IP-based authentication after perfSONAR 3.5.1 automatic upgrade

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] problems writing to central MA using IP-based authentication after perfSONAR 3.5.1 automatic upgrade


Chronological Thread 
  • From: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>
  • To: Antoine Delvaux <>
  • Cc: perfsonar-user <>, Andrew Lake <>
  • Subject: Re: [perfsonar-user] problems writing to central MA using IP-based authentication after perfSONAR 3.5.1 automatic upgrade
  • Date: Tue, 15 Mar 2016 15:21:07 +0000
  • Accept-language: en-US

Hi Antoine,

I saw the email you sent earlier today after I sent my previous. Per your
instructions I’ve been able to successfully complete the upgrade. I will
check my Central MA later today to see if the database is getting updated
with the LivaX test results. One question I have is that it wasn’t just
owamp data that wasn’t getting updated in the Central MA, but the
bwctl/iperf test results were also not updating. Will the 3.5.1-1 upgrade
resolve both issues?

Thanks!!
-George


# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
libperfsonar-perl libperfsonar-sls-perl linux-headers-generic-lts-trusty
linux-image-generic-lts-trusty linux-signed-image-generic-lts-trusty
perfsonar-lsregistrationdaemon
perfsonar-oppd-server perfsonar-oppd-shared perfsonar-regulartesting
The following packages will be upgraded:
linux-generic-lts-trusty linux-libc-dev linux-signed-generic-lts-trusty
owamp-client owamp-server
5 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
Need to get 470 kB/1,331 kB of archives.
After this operation, 3,072 B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://downloads.perfsonar.net/debian/ perfsonar-wheezy-3.5/main
owamp-client amd64 3.5.0-2~bpo70+1 [283 kB]
Get:2 http://downloads.perfsonar.net/debian/ perfsonar-wheezy-3.5/main
owamp-server amd64 3.5.0-2~bpo70+1 [187 kB]
Fetched 470 kB in 1s (245 kB/s)
(Reading database ... 151275 files and directories currently installed.)
Preparing to replace linux-generic-lts-trusty 3.13.0.79.71 (using
.../linux-generic-lts-trusty_3.13.0.83.75_amd64.deb) ...
Unpacking replacement linux-generic-lts-trusty ...
Preparing to replace linux-libc-dev 3.2.0-99.139 (using
.../linux-libc-dev_3.2.0-101.141_amd64.deb) ...
Unpacking replacement linux-libc-dev ...
Preparing to replace linux-signed-generic-lts-trusty 3.13.0.79.71 (using
.../linux-signed-generic-lts-trusty_3.13.0.83.75_amd64.deb) ...
Unpacking replacement linux-signed-generic-lts-trusty ...
Preparing to replace owamp-client 3.5.0-1~bpo70+1 (using
.../owamp-client_3.5.0-2~bpo70+1_amd64.deb) ...
Unpacking replacement owamp-client ...
Preparing to replace owamp-server 3.4.14-1 (using
.../owamp-server_3.5.0-2~bpo70+1_amd64.deb) ...
* Stopping OWAMP server owampd

[ OK ]
Moving obsolete conffile /etc/init.d/owampd out of the way...
Unpacking replacement owamp-server ...
dpkg: warning: unable to delete old directory '/etc/owampd': Directory not
empty
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up linux-generic-lts-trusty (3.13.0.83.75) ...
Setting up linux-libc-dev (3.2.0-101.141) ...
Setting up linux-signed-generic-lts-trusty (3.13.0.83.75) ...
Setting up owamp-client (3.5.0-2~bpo70+1) ...
Setting up owamp-server (3.5.0-2~bpo70+1) ...
Removing obsolete conffile /etc/init.d/owampd ...
* Starting OWAMP server owamp-server




On 3/15/16, 11:06 AM, "Antoine Delvaux"
<>
wrote:

>Hi George,
>
>Your problem seems to be specific to Ubuntu upgrades from 3.5 to 3.5.1.
>
>Have you seen my other message on the list? Try to do an 'apt-get
>update' and 'apt-get upgrade' again, we have released new packages
>correcting these bugs, hopefully, this morning.
>
>Thanks,
>
>Antoine.
>
>> Le 15 mars 2016 à 13:57, Uhl, George D. (GSFC-423.0)[SGT INC]
>><>
>> a écrit :
>>
>> Hi Andy,
>>
>> I’m still trying to get both my LivaX hosts to successfully write data
>>to
>> the Central MA since the 3.5.1-1 code release. I’m using Username/API
>>key
>> authentication. I’ve performed an ‘apt-get update’ and an ‘apt-get
>> upgrade’ but the upgrade fails on the owamp-server and
>> libperfsonar-sls-perl packages. The tests are still running on the
>>hosts
>> and they are attempting to write the the Central MA on port 443, but the
>> data never is recorded in the database.
>>
>> Thanks,
>> George
>>
>> On 3/14/16, 9:51 AM, "Uhl, George D. (GSFC-423.0)[SGT INC]"
>> <>
>> wrote:
>>
>>> Hi Antoine,
>>>
>>> Here is the output of the Œapt-get upgrade¹. The output is much
>>>shorter
>>> this time since this upgrade only dealt with the previous failures.
>>>Could
>>> this failure be a result of running Ubuntu 12.04.5 vs 14.x?
>>>
>>> Thanks,
>>> George
>>>
>>>
>>> # apt-get upgrade
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> The following packages have been kept back:
>>> libperfsonar-perl linux-headers-generic-lts-trusty
>>> linux-image-generic-lts-trusty linux-signed-image-generic-lts-trusty
>>> perfsonar-lsregistrationdaemon perfsonar-oppd-server
>>>perfsonar-oppd-shared
>>> perfsonar-regulartesting
>>> The following packages will be upgraded:
>>> libperfsonar-sls-perl owamp-server
>>> 2 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
>>> 110 not fully installed or removed.
>>> Need to get 0 B/210 kB of archives.
>>> After this operation, 74.8 kB of additional disk space will be used.
>>> Do you want to continue [Y/n]? Y
>>> (Reading database ... 181396 files and directories currently
>>>installed.)
>>> Preparing to replace owamp-server 3.4.14-1 (using
>>> .../owamp-server_3.5.0-1~bpo70+1_amd64.deb) ...
>>> * Stopping OWAMP server owampd
>>>
>>> [ OK ]
>>> update-rc.d: /etc/init.d/owampd exists during rc.d purge (use -f to
>>>force)
>>> dpkg: error processing
>>> /var/cache/apt/archives/owamp-server_3.5.0-1~bpo70+1_amd64.deb
>>>(--unpack):
>>> subprocess new pre-installation script returned error exit status 1
>>> Reinstalling /etc/owampd/owampd.conf that was moved away
>>> Reinstalling /etc/owampd/owampd.limits that was moved away
>>> * Starting OWAMP server owampd
>>>
>>> [ OK ]
>>> Preparing to replace libperfsonar-sls-perl 3.5.0-1 (using
>>> .../libperfsonar-sls-perl_3.5.1.1-1~bpo70+1_all.deb) ...
>>> Unpacking replacement libperfsonar-sls-perl ...
>>> dpkg: error processing
>>> /var/cache/apt/archives/libperfsonar-sls-perl_3.5.1.1-1~bpo70+1_all.deb
>>> (--unpack):
>>> trying to overwrite
>>>
>>>'/usr/share/perl5/perfSONAR_PS/Client/LS/PSQueryObjects/PSPersonQueryObj
>>>ec
>>> t
>>> .pm', which is also in package libperfsonar-perl 3.5.0-1
>>> Errors were encountered while processing:
>>> /var/cache/apt/archives/owamp-server_3.5.0-1~bpo70+1_amd64.deb
>>> /var/cache/apt/archives/libperfsonar-sls-perl_3.5.1.1-1~bpo70+1_all.deb
>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>> root@liva-ow1-1g:~#
>>>
>>>
>>>
>>> On 3/14/16, 9:23 AM, "Antoine Delvaux"
>>> <>
>>> wrote:
>>>
>>>>
>>>>> Le 14 mars 2016 à 13:11, Uhl, George D. (GSFC-423.0)[SGT INC]
>>>>> <>
>>>>> a écrit :
>>>>>
>>>>> Antoine,
>>>>>
>>>>> I had done the 'apt-get update¹ previously but not an 'apt-get
>>>>> upgrade¹.
>>>>> I did both and during the upgrade process for both LivaX hosts I
>>>>> received
>>>>> the following error:
>>>>>
>>>>> Rebuilding /usr/share/applications/bamf.index...
>>>>> Processing triggers for gnome-menus ...
>>>>> Processing triggers for hicolor-icon-theme ...
>>>>> Processing triggers for libglib2.0-0 ...
>>>>> Errors were encountered while processing:
>>>>> /var/cache/apt/archives/owamp-server_3.5.0-1~bpo70+1_amd64.deb
>>>>>
>>>>>/var/cache/apt/archives/libperfsonar-sls-perl_3.5.1.1-1~bpo70+1_all.de
>>>>>b
>>>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>>
>>>> Do you have more output from this error? This was probably included a
>>>> bit before the final line, during the actual installation of those 2
>>>> packages.
>>>>
>>>> You can also run again the `apt-get upgrade` to see what happens, it
>>>> shouldn't make things any worse.
>>>>
>>>> Cheers,
>>>>
>>>> Antoine.
>>>>
>>>
>>
>




Archive powered by MHonArc 2.6.16.

Top of Page