LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 12-31-2012, 02:06 PM   #1
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Rep: Reputation: 44
Unhappy knowledgetree suddenly stopped working (cannot login)


Im at wits' end with my knowledgetree install. Its been working flawlessly for years, then suddenly it stopped working. It stopped within the last 2 months or so since Ive used it around September and was working more than fine.

Basically, I cant login. I can access the login page, enter my username & password, and if I either click "Login" or press enter, the credentials disappears and I just stay on the login page. No "wrong username/password" error messages, nothing. Before when I mistyped something, I would see a yellow box saying "Wrong username or password" but now there is nothing.

Searching my server's logs, I cant find anything useful (or out of the ordinary). The only thing I can think of is fiddling with Apache's config about 3 weeks ago to install newznab which somehow required a virtualhost to run..

The php log file has tons or warnings and deprecated stuff from knowledgetree but if I recall correctly, there warnings were there since install about 2 years ago so I dont think they are related.

My apache VH file looks like:

Code:
NameVirtualHost *:80

<VirtualHost *:80>
    ServerName localhost
    DocumentRoot /var/www/htdocs/
</VirtualHost>

<VirtualHost *:80>
    DocumentRoot /var/www/htdocs/horde4
</VirtualHost>

<VirtualHost *:80>
    DocumentRoot /var/www/htdocs/knowledgetree
        <Directory /var/www/htdocs/knowledgetree>
                Options FollowSymLinks
                Order allow,deny
                Allow from all
        </Directory>
</VirtualHost>

<VirtualHost *:80>
	ServerName newznabplus
	<Directory /var/www/htdocs/newznabplus/www/>
		Options FollowSymLinks
		AllowOverride All
		Order allow,deny
		allow from all
	</Directory>
	DocumentRoot /var/www/htdocs/newznabplus/www
</VirtualHost>
If its relevant, my php log looks like (the last few lines):

Code:
[31-Dec-2012 14:56:01] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/zend/lib/php_extensions/imap.so' - libgssapi_krb5.so.2: cannot open shared object file: No such file or directory in Unknown on line 0
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/lib/validation/customerrorviewer.inc.php on line 44
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/lib/validation/customerrorhandler.php on line 44
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/Config.php on line 79
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/Config.php on line 165
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/Config/Container.php on line 107
[31-Dec-2012 14:56:01] PHP Warning:  The magic method __get() must have public visibility and cannot be static in /var/www/htdocs/knowledgetree/search2/indexing/indexerCore.inc.php on line 99
[31-Dec-2012 14:56:01] PHP Warning:  The magic method __set() must have public visibility and cannot be static in /var/www/htdocs/knowledgetree/search2/indexing/indexerCore.inc.php on line 119
[31-Dec-2012 14:56:01] PHP Warning:  The magic method __get() must have public visibility and cannot be static in /var/www/htdocs/knowledgetree/search2/indexing/indexerCore.inc.php on line 151
[31-Dec-2012 14:56:01] PHP Warning:  The magic method __set() must have public visibility and cannot be static in /var/www/htdocs/knowledgetree/search2/indexing/indexerCore.inc.php on line 165
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/ktapi/ktapi.inc.php on line 752
[31-Dec-2012 14:56:01] PHP Warning:  session_start(): Cannot send session cookie - headers already sent by (output started at /var/www/htdocs/knowledgetree/lib/validation/customerrorviewer.inc.php:44) in /var/www/htdocs/knowledgetree/ktapi/ktapi.inc.php on line 44
[31-Dec-2012 14:56:01] PHP Warning:  session_start(): Cannot send session cache limiter - headers already sent (output started at /var/www/htdocs/knowledgetree/lib/validation/customerrorviewer.inc.php:44) in /var/www/htdocs/knowledgetree/ktapi/ktapi.inc.php on line 44
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/lib/documentmanagement/documentutil.inc.php on line 248
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/lib/i18n/i18nregistry.inc.php on line 49
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/lib/browse/columnregistry.inc.php on line 48
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/ktapi/KTAPISession.inc.php on line 401
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/ktapi/KTAPISession.inc.php on line 446
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/ktapi/KTAPISession.inc.php on line 448
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/ktapi/KTAPISession.inc.php on line 525
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/ktwebservice/KTDownloadManager.inc.php on line 163
[31-Dec-2012 14:56:01] PHP Warning:  The magic method __get() must have public visibility and cannot be static in /var/www/htdocs/knowledgetree/ktapi/KTAPIAcl.inc.php on line 65
[31-Dec-2012 14:56:01] PHP Warning:  The magic method __set() must have public visibility and cannot be static in /var/www/htdocs/knowledgetree/ktapi/KTAPIAcl.inc.php on line 85
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/DB.php on line 310
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/DB.php on line 384
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/DB.php on line 890
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/DB/common.php on line 958
[31-Dec-2012 14:56:01] PHP Deprecated:  Assigning the return value of new by reference is deprecated in /var/www/htdocs/knowledgetree/thirdparty/pear/DB/common.php on line 1150
Its a bummer, I need this to work for my administrative stuff... Since the company who used to make knowledgetree decided to use the open-source community work to create an entire commercial monster, no more forums, no more community, no more opensource...

If there are people out there who could help me, Id appreciate more than you can imagine..

Last edited by lpallard; 12-31-2012 at 02:10 PM.
 
Old 12-31-2012, 09:28 PM   #2
kbp
Senior Member
 
Registered: Aug 2009
Posts: 3,758

Rep: Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643
I haven't touched KT for years but you could try adding custom logging to your vhost config to separate out any KT stuff:

Code:
<VirtualHost *:80>
    DocumentRoot /var/www/htdocs/knowledgetree
    ErrorLog logs/kt-error_log
    CustomLog logs/kt-access_log common
    
    <Directory /var/www/htdocs/knowledgetree>
        Options FollowSymLinks
        Order allow,deny
        Allow from all
    </Directory>
</VirtualHost>
 
Old 12-31-2012, 11:12 PM   #3
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Original Poster
Rep: Reputation: 44
Unfortunately, adding these lines for the logs doesnt work. The logs are staying empty. Nothing in them..

Strange, maybe I am paranoid, but would the fact that KT has become commercial only had something to do with this????
 
Old 12-31-2012, 11:32 PM   #4
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Original Poster
Rep: Reputation: 44
I think it may have something to do with the requirement for newznab for innodb databases... Since I installed KT, I was using slackware's default mysqld configuration (MyISAM I suppose???) until I installed newznab. Then I changed the "default-storage-engine" parameter within /etc/my.cnf to InnoDB and restarted mysqld.

All seems to have worked fine for my 9 other databases... No application has reported problems so far and I am using them profusely (Horde, rssLounge, MediaWiki, zoneminder...)

From an old cached thread on KT's forums:

Quote:
KnowledgeTree requires transaction support in your database. That means InnoDB tables in MySQL. If you're using the stack installer, that should be available.

If not, you might need to configure MySQL to enable InnoDB tables or (particularly on Windows using MySQL binaries) install the mysql-max binaries.
I am confused because I am pretty sure the InnoDB parameter wasnt there before and KT was working just fine. Maybe mysql's default storage is InnoDB in slackware after all?

Is there any way to determine if its not the database creating problems?? If I could eliminate the mysql/database side, that would help..

Thanks!!

Last edited by lpallard; 12-31-2012 at 11:35 PM.
 
Old 12-31-2012, 11:44 PM   #5
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Original Poster
Rep: Reputation: 44
Around Dec. 20, I ran out of disk space where the databases were stored. I have found this in mysql's logs:

Code:
121216 12:45:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121216 12:45:43 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
121216 12:45:44  InnoDB: Started; log sequence number 0 434952744
121216 12:45:45 [Note] Event Scheduler: Loaded 0 events
121216 12:45:45 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.46-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  Source distribution
121220 19:38:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121220 19:38:21 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121220 19:38:21  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 488964710, file name ./mysql-bin.000461
121220 19:38:24  InnoDB: Started; log sequence number 0 438260344
121220 19:38:24 [Note] Recovering after a crash using mysql-bin
121220 19:38:38 [Note] Starting crash recovery...
121220 19:38:38 [Note] Crash recovery finished.
121220 19:38:38 [Note] Event Scheduler: Loaded 0 events
121220 19:38:38 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.46-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  Source distribution
121224 13:23:30 [ERROR] /usr/libexec/mysqld: Disk is full writing '/var/lib/mysql/newznab/parts.MYI' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
121224 13:23:30 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:30:04 [ERROR] /usr/libexec/mysqld: Disk is full writing './mysql-bin.000464' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
121224 13:30:04 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:33:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:40:04 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:43:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:50:04 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:53:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:00:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:03:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:10:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:13:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:20:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:23:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:30:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:33:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:40:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:43:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:50:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:53:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:00:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:03:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:10:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:13:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:20:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:23:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:30:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:33:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:40:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:43:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:50:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:53:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:00:07 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:03:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:10:07 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:13:33 [ERROR] /usr/libexec/m121224 23:42:15  InnoDB: Starting shutdown...
121224 23:42:17  InnoDB: Shutdown completed; log sequence number 0 440834774
121224 23:42:17 [Note] /usr/libexec/mysqld: Shutdown complete
Could the database for KT be corrupted??
 
Old 01-01-2013, 02:09 AM   #6
kbp
Senior Member
 
Registered: Aug 2009
Posts: 3,758

Rep: Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643
Assuming you've freed up space the db should recover .. is there anything further in the logs ?
 
Old 01-01-2013, 09:49 AM   #7
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Original Poster
Rep: Reputation: 44
I went through the whole log line by line and prior to the code below, nothing to flag, but since the 16th of dec (which includes the log output of my first post):

Code:
121216 12:45:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121216 12:45:43 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
121216 12:45:44  InnoDB: Started; log sequence number 0 434952744
121216 12:45:45 [Note] Event Scheduler: Loaded 0 events
121216 12:45:45 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.46-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  Source distribution
121220 19:38:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121220 19:38:21 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121220 19:38:21  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 488964710, file name ./mysql-bin.000461
121220 19:38:24  InnoDB: Started; log sequence number 0 438260344
121220 19:38:24 [Note] Recovering after a crash using mysql-bin
121220 19:38:38 [Note] Starting crash recovery...
121220 19:38:38 [Note] Crash recovery finished.
121220 19:38:38 [Note] Event Scheduler: Loaded 0 events
121220 19:38:38 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.46-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  Source distribution
121224 13:23:30 [ERROR] /usr/libexec/mysqld: Disk is full writing '/var/lib/mysql/newznab/parts.MYI' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
121224 13:23:30 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:30:04 [ERROR] /usr/libexec/mysqld: Disk is full writing './mysql-bin.000464' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
121224 13:30:04 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:33:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:40:04 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:43:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:50:04 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 13:53:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:00:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:03:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:10:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:13:31 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:20:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:23:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:30:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:33:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:40:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:43:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:50:05 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 14:53:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:00:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:03:32 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:10:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:13:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:20:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:23:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:30:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:33:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:40:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:43:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:50:06 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 15:53:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:00:07 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:03:33 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:10:07 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 16:13:33 [ERROR] /usr/libexec/m121224 23:42:15  InnoDB: Starting shutdown...
121224 23:42:17  InnoDB: Shutdown completed; log sequence number 0 440834774
121224 23:42:17 [Note] /usr/libexec/mysqld: Shutdown complete

121224 23:42:17 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121224 23:43:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121224 23:43:29 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
121224 23:43:29 [Warning] Can't create test file /var/lib/mysql/lhost2.lower-test
121224 23:43:29  InnoDB: Started; log sequence number 0 440834774
/usr/libexec/mysqld: Disk is full writing './mysql-bin.~rec~' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
/usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121224 23:44:30 [Note] Event Scheduler: Loaded 0 events
121224 23:44:30 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.46-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  Source distribution
121224 23:53:45 [Note] /usr/libexec/mysqld: Normal shutdown

121224 23:53:45 [Note] Event Scheduler: Purging the queue. 0 events
121224 23:53:45  InnoDB: Starting shutdown...
121224 23:53:50  InnoDB: Shutdown completed; log sequence number 0 440834784
121224 23:53:50 [Note] /usr/libexec/mysqld: Shutdown complete

121224 23:53:50 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121225 00:00:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121225  0:00:46 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
121225  0:00:47  InnoDB: Started; log sequence number 0 440834784
121225  0:00:47 [Note] Event Scheduler: Loaded 0 events
121225  0:00:47 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.46-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  Source distribution
121225  0:08:36 [ERROR] /usr/libexec/mysqld: Disk is full writing '/var/lib/mysql/newznab/binaries.MYI' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
121225  0:08:36 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121225  0:18:36 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121225  0:28:37 [ERROR] /usr/libexec/mysqld: Retry in 60 secs. Message reprinted in 600 secs
121225 00:38:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121225  0:38:57 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
121225  0:38:57 [Warning] Can't create test file /var/lib/mysql/lhost2.lower-test
121225  0:38:57 [Warning] Can't create test file /var/lib/mysql/lhost2.lower-test
/usr/libexec/mysqld: File './mysql-bin.~rec~' not found (Errcode: 28)
121225  0:38:57 [ERROR] MYSQL_BIN_LOG::open_purge_index_file failed to open register  file.
121225  0:38:57 [ERROR] MYSQL_BIN_LOG::open_index_file failed to sync the index file.
121225  0:38:57 [ERROR] Aborting

121225  0:38:57 [Note] /usr/libexec/mysqld: Shutdown complete

121225 00:38:57 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121225 00:49:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121225  0:49:01 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121225  0:49:01  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 620085545, file name ./mysql-bin.000464
121225  0:49:02  InnoDB: Started; log sequence number 0 440834794
121225  0:49:02 [Note] Recovering after a crash using mysql-bin
121225  0:49:05 [Note] Starting crash recovery...
121225  0:49:05 [Note] Crash recovery finished.
121225  0:49:05 [Note] Event Scheduler: Loaded 0 events
121225  0:49:05 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.46-log'  socket: '/var/run/mysql/mysql.sock'  port: 3306  Source distribution
121225  0:53:52 [Note] /usr/libexec/mysqld: Normal shutdown
121225  0:53:52 [Note] Event Scheduler: Purging the queue. 0 events
121225  0:53:52  InnoDB: Starting shutdown...
121225  0:53:57  InnoDB: Shutdown completed; log sequence number 0 440834794
121225  0:53:57 [Note] /usr/libexec/mysqld: Shutdown complete
121225 00:53:57 mysqld_safe mysqld from pid file /var/lib/mysql/lhost2.pid ended
Strange because first of all, the file "mysql-bin.000464" pertains to newznab so if an app should be suffering from those events it should be newznab right? Using phpMyadmin, I can browse KT's database without problems and even change values in the tables. I did however noticed that the database is now a mix of MyISAM & InnoDB tables... Normal? Same applies to all other databases although no other app has been behaving in a weird manner...

If there are no significant problems with mysql or if the database backend is not to blame, next I am suspecting that KT got screwed up and confused when I put it in a virtualhost in apache. When I installed KT about 2 years ago, I had no idea how apache worked.. I simply used the default slackware config (I guess no VH, just a webroot). During the install wizard of KT it probably created symlinks and other variables that were formulated to match my apache's config back then.

An old forum thread on KT's forums indicated the fact that even changing the values in config.ini did not do anything as this file was only used for install wizard at setup time and not to actually run KT. If you want to change settings or parameters, you have to modify them in KT's database under the "config_settings" table... I am there at this point..

What do you guys think??
 
Old 01-01-2013, 06:59 PM   #8
kbp
Senior Member
 
Registered: Aug 2009
Posts: 3,758

Rep: Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643
Hmm .. I think there have been too many things going on, quickest resolution may be to export the db, back up the data and go for a reinstall.
 
1 members found this post helpful.
Old 01-09-2013, 05:14 PM   #9
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Original Poster
Rep: Reputation: 44
oK I have *managed* to find the source files (the install files) somewhere on the web, and extracted everything in the server's webroot. Then if I remember correctly, I installed KT by accessing knowledgetree/setup which would give me a setup wizard and steps to follow. Now I get

Code:
Notice: Use of undefined constant APP_NAME - assumed 'APP_NAME' in /var/www/htdocs/knowledgetree/setup/precheckup.php on line 272
APP_NAME Checkup

This checkup allows you to check that your environment is ready to support a
Notice: Use of undefined constant APP_NAME - assumed 'APP_NAME' in /var/www/htdocs/knowledgetree/setup/precheckup.php on line 275
APP_NAME installation, and that you can proceed to configure your system. Red items are things to fix. Orange items means you may not be having the ultimate experience unless the support is added. Green items means you're ready to go in this area. You can check back here to see if anything has changed in your environment if you have any problems.
.htaccess file

You can let
Notice: Use of undefined constant APP_NAME - assumed 'APP_NAME' in /var/www/htdocs/knowledgetree/setup/precheckup.php on line 284
APP_NAME manage the PHP settings that apply to the
Notice: Use of undefined constant APP_NAME - assumed 'APP_NAME' in /var/www/htdocs/knowledgetree/setup/precheckup.php on line 285
APP_NAME application (it won't affect your other applications) by configuring your web server to use the .htaccess files that come with
Notice: Use of undefined constant APP_NAME - assumed 'APP_NAME' in /var/www/htdocs/knowledgetree/setup/precheckup.php on line 287
APP_NAME. This will ensure that the settings for
Notice: Use of undefined constant APP_NAME - assumed 'APP_NAME' in /var/www/htdocs/knowledgetree/setup/precheckup.php on line 287
APP_NAME(detailed below) are set up for optimal, reliable performance.

Your web server is set up to use the .htaccess files.

Fatal error: Class 'KTUtil' not found in /var/www/htdocs/knowledgetree/setup/precheckup.php on line 294
I tried to access knowledgetree/tests and I get

Code:
Forbidden

You don't have permission to access /knowledgetree/tests/ on this server.
Seems this is either because KT wasnt designed or written to work in a virtualhost, or my apache config is messed up...

Can you (or anyone else) provide some help?? This is causing a major disruption in my work.. I wish I would NEVER tried that KT crap...
 
Old 01-09-2013, 06:41 PM   #10
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Original Poster
Rep: Reputation: 44
Ok Ive found some interesting info on KT's forum cached forum threads (thanks Google), adding

Code:
AddType text/html .php .phps
AddHandler application/x-httpd-php .php
AddHandler application/x-httpd-php-source .phps
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
to the virtualhost config allowed me to access the setup page.. At least...

Then I follow the wizard, and I am offered 3 options:

Install KnowledgeTree (Default)
Upgrade KnowledgeTree Stack Install
Upgrade KnowledgeTree Source Only Install


The first option (Install KT) will not allow me to reuse the existing database... The setup wizard says

Code:
Database Already Exists, specify a different name
Not acceptable as I need to reuse the current DB.

The second option (Upgrade KT stack install) ask me to enter the full path of the installation I wish to upgrade... I enter the current directory of the former KT install (in my case /var/www/htdocs/ktree) but I get a red error message saying:

Code:
KnowledgeTree installation configuration file not found
I tried

Code:
/var/www/htdocs/ktree/config
But same result.

Finally, the third option (Upgrade KT Source Only Install) ask me for admin credentials to upgrade the DB. I tried every combination of credentials I could think of (mysql's admin user, KT, admin user, KT's normal user, the server's root account) but I always get an error saying:

Code:
Could Not Authenticate User
What else can I do?

Last edited by lpallard; 01-09-2013 at 06:44 PM.
 
Old 01-12-2013, 11:48 AM   #11
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 970

Original Poster
Rep: Reputation: 44
Fixed.... I destroyed everything (created backups prior to doing so), and re-installed KT, reimported the database and the documents folder, and its working fine now... Not sure though why KT did not like the Apache's config changes. Poorly coded application I am thinking but Im not a coder myself so I am restricting my comments.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[FIXED] Laptop keyboard and touchpad suddenly stopped working on at login screen frankquestion Linux - Software 1 07-27-2009 12:08 PM
Printer stopped working suddenly? NightSky Slackware 11 12-26-2008 04:50 AM
apache suddenly stopped working newlinuxnewbie Linux - General 21 11-25-2005 03:56 PM
Internet suddenly stopped working. figster Linux - Newbie 2 08-29-2005 05:18 PM
yum suddenly stopped working DJOtaku Fedora 3 05-01-2005 11:38 AM


All times are GMT -5. The time now is 09:10 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration