• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Problems updating license

M

mrzottel

Guest
Hello,

I have some problems with updating my license file. When I try to update it manually in the license manager with "get keys now" (or similar, I have the german version), the center of the screen just turns white.

In the errorlog, the following lines appear:

Code:
Activation request for 'sapp-PPWSE-1' added
/opt/psa/admin/bin/httpsd: relocation error: /lib/tls/libnss_dns.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
Activation request for 'sapp-PPWSE-1' added
/opt/psa/admin/bin/httpsd: relocation error: /lib/tls/libnss_dns.so.2: symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

The system is a debian 3.1 stable. I think those problems started arround the time glibc got updated to 2.3.6...

Any suggestions?
 
Ok, I feel quite stupid, answering my own posting just a few minutes after I posted it. But I just solved the problem. As I googled for the problem for quite some time before, I came accross the "restart the webserver" solution. So I did a
Code:
/etc/init.d/psa restart
- without any success. Thus I dropped that solution for me.

Out of boredom while waiting for an answer here, I stopped the psa service with
Code:
/etc/init.d/psa stop
- and restartet it right away with
Code:
/etc/init.d/psa start.

I guess, this did a _real_ restart of the http daemon - the problem was gone ;)

Bye
mrzottel
 
Back
Top