• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

HTTPD_LOG_D not defined

D

DJ Digital Gem

Guest
I recently completed an update (Dec 26th) and it was then that my PSA service failed to run and I have tried several times to get it restarted but to no avail.

Here's a little more info on what I am seeing.

First, when I run a PSA service start, here's what I see:
Reloading configuration: [ OK ]
Starting psa-spamassassin service: [ OK ]
/usr/local/psa/admin/bin/httpsdctl start: httpd (pid 21763) already running
Starting Plesk: [ OK ]
Starting up drwebd: Dr.Web (R) daemon for Linux/Plesk Edition v4.33 (4.33.0.09211)
Copyright (c) Igor Daniloff, 1992-2005
Doctor Web, Ltd., Moscow, Russia
Support service: http://support.drweb.com
To purchase: http://buy.drweb.com

Daemon version: 4.33.0 <API:2.1>
Engine version: 4.33 <API:2.1>
Loading /var/drweb/bases/drwtoday.vdb - Ok, virus records: 546
Loading /var/drweb/bases/drw43367.vdb - Ok, virus records: 1834
Loading /var/drweb/bases/drw43366.vdb - Ok, virus records: 4015
Loading /var/drweb/bases/drw43365.vdb - Ok, virus records: 1342
Loading /var/drweb/bases/drw43364.vdb - Ok, virus records: 1335
Loading /var/drweb/bases/drw43363.vdb - Ok, virus records: 1152
Loading /var/drweb/bases/drw43362.vdb - Ok, virus records: 1006
Loading /var/drweb/bases/drw43361.vdb - Ok, virus records: 879
Loading /var/drweb/bases/drw43360.vdb - Ok, virus records: 988
Loading /var/drweb/bases/drw43359.vdb - Ok, virus records: 1205
Loading /var/drweb/bases/drw43358.vdb - Ok, virus records: 1139
Loading /var/drweb/bases/drw43357.vdb - Ok, virus records: 1302
Loading /var/drweb/bases/drw43356.vdb - Ok, virus records: 1332
Loading /var/drweb/bases/drw43355.vdb - Ok, virus records: 2456
Loading /var/drweb/bases/drw43354.vdb - Ok, virus records: 1283
Loading /var/drweb/bases/drw43353.vdb - Ok, virus records: 795
Loading /var/drweb/bases/drw43352.vdb - Ok, virus records: 2016
Loading /var/drweb/bases/drw43351.vdb - Ok, virus records: 941
Loading /var/drweb/bases/drw43350.vdb - Ok, virus records: 1020
Loading /var/drweb/bases/drw43349.vdb - Ok, virus records: 1008
Loading /var/drweb/bases/drw43348.vdb - Ok, virus records: 1096
Loading /var/drweb/bases/drw43347.vdb - Ok, virus records: 707
Loading /var/drweb/bases/drw43346.vdb - Ok, virus records: 1428
Loading /var/drweb/bases/drw43345.vdb - Ok, virus records: 1358
Loading /var/drweb/bases/drw43344.vdb - Ok, virus records: 694
Loading /var/drweb/bases/drw43343.vdb - Ok, virus records: 1186
Loading /var/drweb/bases/drw43342.vdb - Ok, virus records: 744
Loading /var/drweb/bases/drw43341.vdb - Ok, virus records: 841
Loading /var/drweb/bases/drw43340.vdb - Ok, virus records: 822
Loading /var/drweb/bases/drw43339.vdb - Ok, virus records: 1071
Loading /var/drweb/bases/drw43338.vdb - Ok, virus records: 989
Loading /var/drweb/bases/drw43337.vdb - Ok, virus records: 855
Loading /var/drweb/bases/drw43336.vdb - Ok, virus records: 1297
Loading /var/drweb/bases/drw43335.vdb - Ok, virus records: 1195
Loading /var/drweb/bases/drw43334.vdb - Ok, virus records: 900
Loading /var/drweb/bases/drw43333.vdb - Ok, virus records: 1381
Loading /var/drweb/bases/drw43332.vdb - Ok, virus records: 1340
Loading /var/drweb/bases/drw43331.vdb - Ok, virus records: 2735
Loading /var/drweb/bases/drw43330.vdb - Ok, virus records: 2078
Loading /var/drweb/bases/drw43329.vdb - Ok, virus records: 2490
Loading /var/drweb/bases/drw43328.vdb - Ok, virus records: 743
Loading /var/drweb/bases/drw43327.vdb - Ok, virus records: 958
Loading /var/drweb/bases/drw43326.vdb - Ok, virus records: 793
Loading /var/drweb/bases/drw43325.vdb - Ok, virus records: 713
Loading /var/drweb/bases/drw43324.vdb - Ok, virus records: 655
Loading /var/drweb/bases/drw43323.vdb - Ok, virus records: 655
Loading /var/drweb/bases/drw43322.vdb - Ok, virus records: 778
Loading /var/drweb/bases/drw43321.vdb - Ok, virus records: 846
Loading /var/drweb/bases/drw43320.vdb - Ok, virus records: 808
Loading /var/drweb/bases/drw43319.vdb - Ok, virus records: 764
Loading /var/drweb/bases/drw43318.vdb - Ok, virus records: 838
Loading /var/drweb/bases/drw43317.vdb - Ok, virus records: 363
Loading /var/drweb/bases/drw43316.vdb - Ok, virus records: 730
Loading /var/drweb/bases/drw43315.vdb - Ok, virus records: 627
Loading /var/drweb/bases/drw43314.vdb - Ok, virus records: 824
Loading /var/drweb/bases/drw43313.vdb - Ok, virus records: 842
Loading /var/drweb/bases/drw43312.vdb - Ok, virus records: 830
Loading /var/drweb/bases/drw43311.vdb - Ok, virus records: 862
Loading /var/drweb/bases/drw43310.vdb - Ok, virus records: 853
Loading /var/drweb/bases/drw43309.vdb - Ok, virus records: 733
Loading /var/drweb/bases/drw43308.vdb - Ok, virus records: 708
Loading /var/drweb/bases/drw43307.vdb - Ok, virus records: 839
Loading /var/drweb/bases/drw43306.vdb - Ok, virus records: 930
Loading /var/drweb/bases/drw43305.vdb - Ok, virus records: 759
Loading /var/drweb/bases/drw43304.vdb - Ok, virus records: 721
Loading /var/drweb/bases/drw43303.vdb - Ok, virus records: 638
Loading /var/drweb/bases/drw43302.vdb - Ok, virus records: 806
Loading /var/drweb/bases/drw43301.vdb - Ok, virus records: 504
Loading /var/drweb/bases/drw43300.vdb - Ok, virus records: 24
Loading /var/drweb/bases/drwebase.vdb - Ok, virus records: 78674
Loading /var/drweb/bases/dwrtoday.vdb - Ok, virus records: 365
Loading /var/drweb/bases/dwr43301.vdb - Ok, virus records: 697
Loading /var/drweb/bases/drwrisky.vdb - Ok, virus records: 1271
Loading /var/drweb/bases/dwntoday.vdb - Ok, virus records: 334
Loading /var/drweb/bases/dwn43306.vdb - Ok, virus records: 781
Loading /var/drweb/bases/dwn43305.vdb - Ok, virus records: 752
Loading /var/drweb/bases/dwn43304.vdb - Ok, virus records: 793
Loading /var/drweb/bases/dwn43303.vdb - Ok, virus records: 766
Loading /var/drweb/bases/dwn43302.vdb - Ok, virus records: 850
Loading /var/drweb/bases/dwn43301.vdb - Ok, virus records: 772
Loading /var/drweb/bases/drwnasty.vdb - Ok, virus records: 4867
Total virus records: 164867
Key file: /opt/drweb/drweb32.key - License key file error!
A path to a valid license key file does not specified.
Plesk authorization failed: HTTP request error [52]
Error: Plesk Software not running.
[FAILED]

So I checked the php.ini file and found a couple of things hosed there; fixed that and restarted services and still got this error. I am wondering if anyone has any information on the HTTPD_LOG_D not defined error, or if anyone else has completed an update recently and had these types of problems. I also found that al of the sudden, after doing this update, my Drweb key has disappeared so there may be something going on with the newest updates I just completed. Here is what was updated:
Download file versions.inf3: 100% done
Download file PSA_8.1.0/plesk-8.1.0-fc4-i386.inf3: 100% done
Checking for system installed packages...done.
Check for components installation status
Reading system installed packages...done.
Download file build-8.1.0-fc4-i386.hdr.gz: 57%..100% done
Download file update-8.1.0-fc4-i386.hdr.gz: 55%..100% done
Resolve components
Get Plesk product packages.
Download file
opt/updater/psa-autoinstaller-3.1.0-build31061201.02.i586.rpm: 28%..77%..100% done
Get system update packages.
Start packages installation
Install package psa-autoinstaller
Installation done.

I have also tried re-installing the VPS and that failed.
 
I was able to resolve some of these issues but I am still getting:

Key file: /opt/drweb/drweb32.key - License key file error! Completed Dec 28, 2006 08:18:46 AM A path to a valid license key file does not specified. Completed Dec 28, 2006 08:18:46 AM Plesk authorization failed: HTTP request error [52] Completed Dec 28, 2006 08:18:46 AM Error: Plesk Software not running. Completed Dec 28, 2006 08:18:46 AM [FAILED]
 
Now I have the PSA started but I am getting a PLESK mis configured error.

It appears this is due to the error I am seeing with the Dr. Web key and I will now have to have this re-installed. Has anyone else had any of these problems with the latest update??
 
I found this related link: http://forum.swsoft.com/showthread.php?threadid=38340

Since I work for the web hosting company I purchased my hosting from, we had an extensive conversation about this and we believe that what may have happened is that when the update was done, it started looking for the drweb32.key file and because our licensing never installed this file, the update is now looking fo rit but it was never installed. Apparently for me the service psa stopall and then restart DID NOT WORK. I have tried this at least ten times over the past two days and one of our admins tried it on my server as well and it is still giving us the error with the Dr Web file.
 
Apparently this fix:

In /etc/init.d/psa

comment out the line,
service_after_psa="drwebd"

then service psa stopall
service psa start

it should start without drweb

This is basically defeating the purpose of even having Dr Web installed but I found out something else that was very interesting as well. When installing the PLESK power packs, Dr Web is a limited license, meaning you can only use it on 7 email accounts and then no more. It looks like what has happened it I had a version of Dr Web that maybe had a generic license but when I did the update, it started looking for the drweb32.key file which is the LICENSE that probably should have been installed when the Dr Web was installed with my PLESK power pack. Get this though.......From what one of our sales guys told me today, SW Soft is telling us that our clients will need to BUY THE LICENSE that they thought they got when they purchased the PLESK power packs. Estimated cost is around $400.
 
That fix got rid of the error when I restarted the services but I still have a message that says my PLESK is mis configured :mad:
 
Originally posted by DJ Digital Gem
That fix got rid of the error when I restarted the services but I still have a message that says my PLESK is mis configured :mad:

Could you give the list of the errors? Just be more specific. Probably I can help in this case.
 
Well, I eventually was able to re-install my VPS but that didn't seem to work right either; it made the "old" directory with NONE of my files there. It's a darn good thing I backed up all my files before I started any of this! For Francuz, check out my first post in this. Every thing's there!
 
Well, another day and another problem. I have gotten rid of all those errors, and gotten most of my 17 gigs of files re-uploaded. When I went to DB Web Admin to get to phpMyAdmin, I got this error: "#1045 - Access denied for user 'pma_xxxxxxx'@'localhost' (using password: YES)"

So there was a "fix" in these forums which said this: "Make sure that Plesk PHPMyAdmin user exists in mysql.user
table and has right password and privileges. Username and password can
be found in $PRODUCT_ROOT_D/admin/htdocs/domains/databases/phpMyAdmin/config.inc.php,
for example:

# cd /usr/local/psa/admin
# grep controluser htdocs/domains/databases/phpMyAdmin/config.inc.php

$cfg['Servers'][$i]['controluser'] = 'USER';

# grep controlpass htdocs/domains/databases/phpMyAdmin/config.inc.php

$cfg['Servers'][$i]['controlpass'] = 'PASSWORD';

# grep pmadb htdocs/domains/databases/phpMyAdmin/config.inc.php

$cfg['Servers'][$i]['pmadb'] = 'DATABASE';

Try to login as this user into MySQL from the command line. If the
password doesn't match, update mysql.user table and set 'PASSWORD' password
for 'USER'. If such user doesn't exist in Mysql, create it with commands like:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow`

mysql> use mysql;
mysql> insert into user values ('localhost','USER',password('PASSWORD'),'N','N','N','N','N','N','N','N','N','N','N','N','N','N','N','N','N','N','N','N','N','','','','',0,0,0);

mysql> INSERT INTO `db` VALUES ('localhost','DATABASE','USER','Y','Y','Y','Y','N','N','N','N','N','N','N','N');
mysql> flush privileges;

Replace USER, PASSWORD and DATABASE with the right values from config.inc.php."

I did this and now when I try to access a DB in phpMyAdmin, it just takes me to PLESK. Any thoughts???
 
Hi,

edit your /etc/psa/psa.conf
Own this:
Code:
NAMED_ZONES_CONF /etc
NAMED_OPTIONS_CONF /etc 
HTTPD_LOG_D /var/log
AWSTATS_TOOLS_D /var/lib
AWSTATS_BIN_D /var/lib
AWSTATS_ETC_D /etc
CURL_CA_BUNDLE_FILE  /usr/include/curl
HTTPD_INCLUDE_D         /etc/httpd/conf

Stop and start your psa.
It works.


regards,

GitS
 
That was done about six posts ago to get rid of the Dr Web error GhostInTheShell. That's not going to change the fact that when I go to my phpMyAdmin, that it takes me to PLESK.
 
Back
Top