Welcome Guest ( Log In | Register)



 
Reply to this topicStart new topic
> Problem Connecting To Phpmyadmin
bittr
post Jul 25 2008, 09:02 PM
Post #1


Member [Level 1]
****

Group: [HOSTED]
Posts: 53
Joined: 16-July 08
From: Brasov
Member No.: 65,085



So... I have a problem connecting with phpMyAdmin from time to time.

More exactly, it happens I think every 2 days.

The error message I get is this:

QUOTE
Warning: session_write_close() [function.session-write-close]: SQLite: session write query failed: database is full in /usr/local/cpanel/base/3rdparty/phpMyAdmin/index.php on line 42

Warning: session_write_close() [function.session-write-close]: Failed to write session data (sqlite). Please verify that the current setting of session.save_path is correct (/var/cpanel/userhomes/cpanelphpmyadmin/sessions/phpsess.sdb) in /usr/local/cpanel/base/3rdparty/phpMyAdmin/index.php on line 42

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/cpanel/base/3rdparty/phpMyAdmin/index.php:42) in /usr/local/cpanel/base/3rdparty/phpMyAdmin/index.php on line 99

I go to phpMyAdmin through CPanel, of course. (just to clarify my steps)

And usualy it starts to work again after like 2 hours, but it's very frustrating that I can't have access to my database when I want.


To mention that the database is functional meanwhile, as my website is working. So there's a problem with phpMyAdmin.

I'm opened for suggestions.
Cheers!
Go to the top of the page
 
+Quote Post
truefusion
post Jul 25 2008, 09:45 PM
Post #2


Ephesians 6:10-17
Group Icon

Group: [MODERATOR]
Posts: 1,917
Joined: 22-June 05
From: The World of Gentoo
Member No.: 8,528



QUOTE(bittr @ Jul 25 2008, 05:02 PM) *
So there's a problem with phpMyAdmin.

It's not a phpMyAdmin problem, it's more of a permissions problem; it never was a phpMyAdmin problem.

QUOTE(bittr @ Jul 25 2008, 05:02 PM) *
I'm opened for suggestions.

Learn MySQL and make your own database administration panel that uses cookies instead of sessions. Otherwise wait for someone to figure out the cause of the problem from the server side like we are waiting. I have assumed that a cron job may be causing this error, but i can't verify it. Starting a support ticket with XistoSupport is useless and pointless (as time has proven) for this problem at the moment, so i don't recommend doing that. It has been said that Opaque would look into it when he gets the chance.

Until then, let's try to keep these topics from duplicating.
Go to the top of the page
 
+Quote Post
bittr
post Jul 25 2008, 10:24 PM
Post #3


Member [Level 1]
****

Group: [HOSTED]
Posts: 53
Joined: 16-July 08
From: Brasov
Member No.: 65,085



Ok, thanks for the answer.

I'm sorry if this was a duplicate topic... I tried to search for a similar thing on the Suggestions forum, but found nothing.


About learning MySQL. Funny.

I've worked a lot with MySQL, but never online, always using Toad or something like that.
I'll try to find something else to use if the problem persists. Thanks again for clearing things up.
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic

Collapse

> Similar Topics

Topics Topics


 



- Lo-Fi Version Time is now: 11th October 2008 - 08:33 PM