Welcome to Geeklog, Anonymous Thursday, October 10 2024 @ 09:55 pm EDT
Geeklog Forums
GL 1.4.1 Member Logout issue and new member registration issue
Status: offline
Tech_Z
Forum User
Junior
Registered: 01/14/08
Posts: 30
Location:Soquel, California
I'm having this problem with logging out it intermittently go to SQL error check error log.
In my error log it shows these error entries for today also these errors began around the first of the month:
Thu 06 Mar 2008 03:24:55 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (161058125,1204802695,'74.6.7.141',1)
Thu 06 Mar 2008 10:45:26 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1475124903,1204829126,'66.249.70.72',1)
Thu 06 Mar 2008 14:02:13 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:09:05 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:12:54 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1259739754,1204841574,'66.249.70.72',1)
Thu 06 Mar 2008 14:24:06 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:25:45 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:32:07 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1989266575,1204842727,'67.170.200.37',1)
I can hit the back button on the browser and hit logout again and it will work properly. I could use a little help digging into this problem.
Also I have a second issue involving the new user registration page. I have noticed that also intermittently when you hit the register button the server pops up
with a "PHP file and what do you want use to open it" Popup if you exit the popup and hit register a second time it will function correctly. So I'm a bit lost here
as I don't know where these problems are arising from.
Any help would be appreciated greatly.
Thanks,
Dennis
In my error log it shows these error entries for today also these errors began around the first of the month:
Thu 06 Mar 2008 03:24:55 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (161058125,1204802695,'74.6.7.141',1)
Thu 06 Mar 2008 10:45:26 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1475124903,1204829126,'66.249.70.72',1)
Thu 06 Mar 2008 14:02:13 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:09:05 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:12:54 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1259739754,1204841574,'66.249.70.72',1)
Thu 06 Mar 2008 14:24:06 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:25:45 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Thu 06 Mar 2008 14:32:07 PST - 1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1989266575,1204842727,'67.170.200.37',1)
I can hit the back button on the browser and hit logout again and it will work properly. I could use a little help digging into this problem.
Also I have a second issue involving the new user registration page. I have noticed that also intermittently when you hit the register button the server pops up
with a "PHP file and what do you want use to open it" Popup if you exit the popup and hit register a second time it will function correctly. So I'm a bit lost here
as I don't know where these problems are arising from.
Any help would be appreciated greatly.
Thanks,
Dennis
10
11
Quote
Status: offline
Tech_Z
Forum User
Junior
Registered: 01/14/08
Posts: 30
Location:Soquel, California
So also to update this a bit I went into PHPMYADMIN and found that at some point something in the gl_sessions Table was changed and it states there seems to be a couple of problems:
This is what I see in the gl_sessions table maybe someone can decipher the error I know I can't although if I know what to change I'm not afraid to edit I can do that part
darn I cant get the table values to flow right in the post so I used "---" to seperate the columns sorry :doh: wish I new a better way to paste this info to read better...
gl_sessions
Field ---------------Type--------------Null-------Default
sess_id -----------int(10)------------No--------0
start_time --------int(10)------------No--------0
remote_ip -------varchar(15) -----No
uid -----------------mediumint( 8 ) ----No--------1
md5_sess_id----varchar( 128 ) ----Yes----NULL
Indexes:
Keyname------------Type---------Cardinality------------Field
PRIMARY----------PRIMARY---------0------------------sess_id
remote_ip_2------UNIQUE-----------0-----------------remote_ip
uid-------------------UNIQUE-----------0--------------------uid
start_time_2-----UNIQUE------------0---------------start_time
sess_id_3---------UNIQUE-----------0----------------sess_id
md5_sess_id_2--UNIQUE--------None-------------md5_sess_id
sess_id------------INDEX-----------None---------------sess_id
start_time---------INDEX-----------None--------------start_time
remote_ip---------INDEX-----------None--------------remote_ip
sess_id_2---------INDEX----------None---------------sess_id
md5_sess_id-----INDEX---------None--------------md5_sess_id
remote_ip_4-------INDEX---------None--------------remote_ip
remote_ip_5------INDEX----------None---------------remote_ip
start_time_3-------INDEX----------None--------------start_time
uid_2----------------INDEX-----------None----------------uid
remote_ip_3----FULLTEXT-------None-------------remote_ip
md5_sess_id_3-FULLTEXT------None----------md5_sess_id
Space usage:
Type-------Usage
Data-------32 Bytes
Index------17,408 Bytes
Overhead--32 Bytes
Effective---17,408 Bytes
Total--------17,440 Bytes
Row Statistics:
Statements---------Value
Format--------------dynamic
Rows-------------------0
Creation--------------Mar 07, 2008 at 03:39 AM
Last update----------Mar 07, 2008 at 04:24 AM
And under all the of these Table values I get these statements which look like errors:
Warning PRIMARY and INDEX keys should not both be set for column `sess_id`
Warning More than one INDEX key was created for column `sess_id`
Warning UNIQUE and INDEX keys should not both be set for column `remote_ip`
Warning More than one INDEX key was created for column `remote_ip`
Warning UNIQUE and INDEX keys should not both be set for column `uid`
Warning UNIQUE and INDEX keys should not both be set for column `start_time`
Warning More than one INDEX key was created for column `start_time`
Warning UNIQUE and INDEX keys should not both be set for column `md5_sess_id`
So this is what I see in the gl_sessions Table which I think is where my problem lies with the Error:
1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1600516717,1204871718,'67.170.200.37',1)
Any and all help will be appreciated tremendously!
Thanks,
Dennis Espindola
http://www.selfautotech.com
This is what I see in the gl_sessions table maybe someone can decipher the error I know I can't although if I know what to change I'm not afraid to edit I can do that part
darn I cant get the table values to flow right in the post so I used "---" to seperate the columns sorry :doh: wish I new a better way to paste this info to read better...
gl_sessions
Field ---------------Type--------------Null-------Default
sess_id -----------int(10)------------No--------0
start_time --------int(10)------------No--------0
remote_ip -------varchar(15) -----No
uid -----------------mediumint( 8 ) ----No--------1
md5_sess_id----varchar( 128 ) ----Yes----NULL
Indexes:
Keyname------------Type---------Cardinality------------Field
PRIMARY----------PRIMARY---------0------------------sess_id
remote_ip_2------UNIQUE-----------0-----------------remote_ip
uid-------------------UNIQUE-----------0--------------------uid
start_time_2-----UNIQUE------------0---------------start_time
sess_id_3---------UNIQUE-----------0----------------sess_id
md5_sess_id_2--UNIQUE--------None-------------md5_sess_id
sess_id------------INDEX-----------None---------------sess_id
start_time---------INDEX-----------None--------------start_time
remote_ip---------INDEX-----------None--------------remote_ip
sess_id_2---------INDEX----------None---------------sess_id
md5_sess_id-----INDEX---------None--------------md5_sess_id
remote_ip_4-------INDEX---------None--------------remote_ip
remote_ip_5------INDEX----------None---------------remote_ip
start_time_3-------INDEX----------None--------------start_time
uid_2----------------INDEX-----------None----------------uid
remote_ip_3----FULLTEXT-------None-------------remote_ip
md5_sess_id_3-FULLTEXT------None----------md5_sess_id
Space usage:
Type-------Usage
Data-------32 Bytes
Index------17,408 Bytes
Overhead--32 Bytes
Effective---17,408 Bytes
Total--------17,440 Bytes
Row Statistics:
Statements---------Value
Format--------------dynamic
Rows-------------------0
Creation--------------Mar 07, 2008 at 03:39 AM
Last update----------Mar 07, 2008 at 04:24 AM
And under all the of these Table values I get these statements which look like errors:
Warning PRIMARY and INDEX keys should not both be set for column `sess_id`
Warning More than one INDEX key was created for column `sess_id`
Warning UNIQUE and INDEX keys should not both be set for column `remote_ip`
Warning More than one INDEX key was created for column `remote_ip`
Warning UNIQUE and INDEX keys should not both be set for column `uid`
Warning UNIQUE and INDEX keys should not both be set for column `start_time`
Warning More than one INDEX key was created for column `start_time`
Warning UNIQUE and INDEX keys should not both be set for column `md5_sess_id`
So this is what I see in the gl_sessions Table which I think is where my problem lies with the Error:
1062: Duplicate entry '1' for key 3. SQL in question: INSERT INTO gl_sessions (sess_id, start_time, remote_ip, uid)
VALUES (1600516717,1204871718,'67.170.200.37',1)
Any and all help will be appreciated tremendously!
Thanks,
Dennis Espindola
http://www.selfautotech.com
6
6
Quote
Status: offline
Tech_Z
Forum User
Junior
Registered: 01/14/08
Posts: 30
Location:Soquel, California
Quote by: Tech_Z[/u]
I'm having this problem with logging out it intermittently go to SQL error check error log.
So I figured out that this issue is caused by my server for the mysql. Not with Geeklog when I performed a traceroute on my database server I'm receiving a Request timed out. So I have a dedicated server but the mysql database is centralized I have support working to address my problem now.
It seems I reeived no replies because this is not a Geeklog related issue.
Thanks,
Dennis
9
14
Quote
Status: offline
jmucchiello
Forum User
Full Member
Registered: 08/29/05
Posts: 985
Quote by: Tech_Z
It seems I reeived no replies because this is not a Geeklog related issue.
I could have sworn I saw a response to this. Glad to hear it isn't a GL problem. But there's still an issue you should resolve. There are too many indexes on that table. All the indexes with _2 and _3 are redundant. You should also check your other tables for similar strangeness.
Oh, and [ code ] [/ code ] (without the spaces) can also be used to on formatted text. Keep the indexes I indicted. Drop all the rest.
Text Formatted Code
Indexes:
Keyname------------Type---------Cardinality------------Field
PRIMARY----------PRIMARY---------0------------------sess_id Keep
remote_ip_2------UNIQUE-----------0-----------------remote_ip
uid-------------------UNIQUE-----------0--------------------uid
start_time_2-----UNIQUE------------0---------------start_time
sess_id_3---------UNIQUE-----------0----------------sess_id
md5_sess_id_2--UNIQUE--------None-------------md5_sess_id
sess_id------------INDEX-----------None---------------sess_id Keep
start_time---------INDEX-----------None--------------start_time Keep
remote_ip---------INDEX-----------None--------------remote_ip Keep
sess_id_2---------INDEX----------None---------------sess_id
md5_sess_id-----INDEX---------None--------------md5_sess_id
remote_ip_4-------INDEX---------None--------------remote_ip
remote_ip_5------INDEX----------None---------------remote_ip
start_time_3-------INDEX----------None--------------start_time
uid_2----------------INDEX-----------None----------------uid
remote_ip_3----FULLTEXT-------None-------------remote_ip
md5_sess_id_3-FULLTEXT------None----------md5_sess_id
8
10
Quote
Status: offline
Tech_Z
Forum User
Junior
Registered: 01/14/08
Posts: 30
Location:Soquel, California
There are too many indexes on that table. All the indexes with _2 and _3 are redundant. You should also check your other tables for similar strangeness.
Oh, and [ code ] [/ code ] (without the spaces) can also be used to on formatted text. Keep the indexes I indicted. Drop all the rest.
Indexes:
Keyname------------Type---------Cardinality------------Field
PRIMARY----------PRIMARY---------0------------------sess_id Keep
remote_ip_2------UNIQUE-----------0-----------------remote_ip
uid-------------------UNIQUE-----------0--------------------uid
start_time_2-----UNIQUE------------0---------------start_time <---------------------
sess_id_3---------UNIQUE-----------0----------------sess_id
md5_sess_id_2--UNIQUE--------None-------------md5_sess_id
[color=red]sess_id------------INDEX-----------None---------------sess_id Keep
start_time---------INDEX-----------None--------------start_time Keep <---------------------------
remote_ip---------INDEX-----------None--------------remote_ip Keep
sess_id_2---------INDEX----------None---------------sess_id
md5_sess_id-----INDEX---------None--------------md5_sess_id
remote_ip_4-------INDEX---------None--------------remote_ip
remote_ip_5------INDEX----------None---------------remote_ip
start_time_3-------INDEX----------None--------------start_time <------------------------
uid_2----------------INDEX-----------None----------------uid[/color]
remote_ip_3----FULLTEXT-------None-------------remote_ip
md5_sess_id_3-FULLTEXT------None----------md5_sess_id
[/p][/QUOTE
Hi jmucchiello, Thanks for the reply
as to the indexes to remove i'm not sure if I understand do you mean remove the ones not underlined
I do have several tables that have this in them:
in the gl_vars table
PRIMARY and INDEX keys should not both be set for column `uid:
[code] Indexes: Documentation
Keyname Type Cardinality Action Field
PRIMARY PRIMARY 14 Edit Drop name
name_2 UNIQUE 14 Edit Drop name
name INDEX None Edit Drop name
value_2 INDEX None Edit Drop value
value FULLTEXT None Edit Drop value
name_3 FULLTEXT None Edit Drop name
Warning PRIMARY and INDEX keys should not both be set for column `name`[/code]
I did [ code ] [/ code ] but this is how displays weird huh
so in the gl_vars table above would you drop the name_3 to fix this error is that one redundant? does the name for instance value become index and drop value_2
I have several tables displaying this problem is there a cause of this issue.
Since my database is on a centralized server I can't have access to the cron auto style GL backup and have to use phpmyadmin
as i'm not a master with the MySQL yet is there anyway I could cause this when creating gzip backups I also have the phpmyadmin protected .htaccess
I want to make sure I understand your instructions as to which to drop! I dont want to ruin my database I can follow your instructions precisely...
I just took a look in some of the other tables and there are alot of these:
gl_access PRIMARY and INDEX keys should not both be set for column `acc_ft_id
gl_article_images Warning PRIMARY and INDEX keys should not both be set for column `ai_sid`
Warning UNIQUE and INDEX keys should not both be set for column `ai_img_num`
Warning UNIQUE and INDEX keys should not both be set for column `ai_filename`
gl_cn_styles Warning PRIMARY and INDEX keys should not both be set for column `id`
Warning More than one INDEX key was created for column `type`
gl_commentcodes PRIMARY and INDEX keys should not both be set for column `code`
gl_commentmodes Warning PRIMARY and INDEX keys should not both be set for column `mode`
Warning UNIQUE and INDEX keys should not both be set for column `name`
gl_cookiecodes Warning PRIMARY and INDEX keys should not both be set for column `cc_value`
Warning UNIQUE and INDEX keys should not both be set for column `cc_descr`
gl_cp_config PRIMARY and INDEX keys should not both be set for column `config_name`
gl_cp_sessions Warning PRIMARY and INDEX keys should not both be set for column `session_id`
Warning UNIQUE and INDEX keys should not both be set for column `cptime`
Warning UNIQUE and INDEX keys should not both be set for column `validation`
gl_dateformats Warning PRIMARY and INDEX keys should not both be set for column `dfid`
Warning UNIQUE and INDEX keys should not both be set for column `description`
Warning UNIQUE and INDEX keys should not both be set for column `format`
gl_events PRIMARY and INDEX keys should not both be set for column `eid`
gl_featurecodes Warning PRIMARY and INDEX keys should not both be set for column `code`
Warning UNIQUE and INDEX keys should not both be set for column `name`
So there are more tables in this state I would like to gut out what doesn't need to be
Any help would be appreciated
Thanks
Dennis
Oh, and [ code ] [/ code ] (without the spaces) can also be used to on formatted text. Keep the indexes I indicted. Drop all the rest.
Text Formatted Code
Indexes:
Keyname------------Type---------Cardinality------------Field
PRIMARY----------PRIMARY---------0------------------sess_id Keep
remote_ip_2------UNIQUE-----------0-----------------remote_ip
uid-------------------UNIQUE-----------0--------------------uid
start_time_2-----UNIQUE------------0---------------start_time <---------------------
sess_id_3---------UNIQUE-----------0----------------sess_id
md5_sess_id_2--UNIQUE--------None-------------md5_sess_id
[color=red]sess_id------------INDEX-----------None---------------sess_id Keep
start_time---------INDEX-----------None--------------start_time Keep <---------------------------
remote_ip---------INDEX-----------None--------------remote_ip Keep
sess_id_2---------INDEX----------None---------------sess_id
md5_sess_id-----INDEX---------None--------------md5_sess_id
remote_ip_4-------INDEX---------None--------------remote_ip
remote_ip_5------INDEX----------None---------------remote_ip
start_time_3-------INDEX----------None--------------start_time <------------------------
uid_2----------------INDEX-----------None----------------uid[/color]
remote_ip_3----FULLTEXT-------None-------------remote_ip
md5_sess_id_3-FULLTEXT------None----------md5_sess_id
Keyname Type Cardinality Action Field
PRIMARY PRIMARY 14 Edit Drop name
name_2 UNIQUE 14 Edit Drop name
name INDEX None Edit Drop name
value_2 INDEX None Edit Drop value
value FULLTEXT None Edit Drop value
name_3 FULLTEXT None Edit Drop name
Warning PRIMARY and INDEX keys should not both be set for column `name`[/code]
I did [ code ] [/ code ] but this is how displays weird huh
so in the gl_vars table above would you drop the name_3 to fix this error is that one redundant? does the name for instance value become index and drop value_2
I have several tables displaying this problem is there a cause of this issue.
Since my database is on a centralized server I can't have access to the cron auto style GL backup and have to use phpmyadmin
as i'm not a master with the MySQL yet is there anyway I could cause this when creating gzip backups I also have the phpmyadmin protected .htaccess
I want to make sure I understand your instructions as to which to drop! I dont want to ruin my database I can follow your instructions precisely...
I just took a look in some of the other tables and there are alot of these:
Text Formatted Code
gl_access PRIMARY and INDEX keys should not both be set for column `acc_ft_id
gl_article_images Warning PRIMARY and INDEX keys should not both be set for column `ai_sid`
Warning UNIQUE and INDEX keys should not both be set for column `ai_img_num`
Warning UNIQUE and INDEX keys should not both be set for column `ai_filename`
gl_cn_styles Warning PRIMARY and INDEX keys should not both be set for column `id`
Warning More than one INDEX key was created for column `type`
gl_commentcodes PRIMARY and INDEX keys should not both be set for column `code`
gl_commentmodes Warning PRIMARY and INDEX keys should not both be set for column `mode`
Warning UNIQUE and INDEX keys should not both be set for column `name`
gl_cookiecodes Warning PRIMARY and INDEX keys should not both be set for column `cc_value`
Warning UNIQUE and INDEX keys should not both be set for column `cc_descr`
gl_cp_config PRIMARY and INDEX keys should not both be set for column `config_name`
gl_cp_sessions Warning PRIMARY and INDEX keys should not both be set for column `session_id`
Warning UNIQUE and INDEX keys should not both be set for column `cptime`
Warning UNIQUE and INDEX keys should not both be set for column `validation`
gl_dateformats Warning PRIMARY and INDEX keys should not both be set for column `dfid`
Warning UNIQUE and INDEX keys should not both be set for column `description`
Warning UNIQUE and INDEX keys should not both be set for column `format`
gl_events PRIMARY and INDEX keys should not both be set for column `eid`
gl_featurecodes Warning PRIMARY and INDEX keys should not both be set for column `code`
Warning UNIQUE and INDEX keys should not both be set for column `name`
So there are more tables in this state I would like to gut out what doesn't need to be
Any help would be appreciated
Thanks
Dennis
11
6
Quote
Status: offline
jmucchiello
Forum User
Full Member
Registered: 08/29/05
Posts: 985
I don't know what you did. But to answer the question I found, I put the word keep next to 4 indexes. All the rest are unneeded.
All of the indexes with _2 or _3 (or more) should be removed. All of the indexes where the type is FULLTEXT should be removed.
It's too bad we'll never know how your databases became so screwed up.
All of the indexes with _2 or _3 (or more) should be removed. All of the indexes where the type is FULLTEXT should be removed.
It's too bad we'll never know how your databases became so screwed up.
10
9
Quote
Status: offline
Tech_Z
Forum User
Junior
Registered: 01/14/08
Posts: 30
Location:Soquel, California
Actually I haven't modified the database as of yet I was waiting for you to give me a little more easy to follow instructions as I was afraid to touch it...
the only thing I have done to the database since installation is back it up! I didn't modify anything because I don't know enough on the administration o MySQL
If you want I can send you a email with my U/N & Password and you can take a closer look if you like to see for yourself I trust you... you seem to know alot about database admin and from there you can see the different plugins that have modified the database and maybe see what may have caused this for yourself. Other than a hack I could not tell you what happened other than a plugin. I dont touch anything but the export backup.
the only thing I have done to the database since installation is back it up! I didn't modify anything because I don't know enough on the administration o MySQL
If you want I can send you a email with my U/N & Password and you can take a closer look if you like to see for yourself I trust you... you seem to know alot about database admin and from there you can see the different plugins that have modified the database and maybe see what may have caused this for yourself. Other than a hack I could not tell you what happened other than a plugin. I dont touch anything but the export backup.
5
12
Quote
Status: offline
jmucchiello
Forum User
Full Member
Registered: 08/29/05
Posts: 985
Unfortunately I just don't have the time for that. Sorry. Maybe someone else can get hands on with you. It should be safe to delete the indexes with numbers at the end (_2 _3, etc). If you have a good backup, restore the backup to a new database and try it there before doing it on your live system.
Good Luck
Good Luck
8
10
Quote
Status: offline
Tech_Z
Forum User
Junior
Registered: 01/14/08
Posts: 30
Location:Soquel, California
Right on jmucchiello, it's all good I don't have another new database to run a test on unless I create one on a domain that doesn't need one. Maybe I'll start over so I can watch the database as I install the plugins so I can verify the problem. this is a new site at www.selfautotech.com and has not even been running long. And still I have not had the extra cash to buy traffic so it shows very little use, heck the forum hasn't even been used. Here shortly I was going start some campaign's to drive traffic but I have been gathering content to add to the site prior to that, as well as spending time on my other sites with GL like www.cruiseinshows.com which has no issues whatsoever with all the same plugins installed minus the ProMenu and DocuWiki it's pretty much identical. I only assume it is something with a plugin destroying the tables otherwise my server must have been hacked. The last install I did was the GL Pro Menu and Docuwiki about 1 1/2 mths ago but it seems the database issues started at the first of this mth by my error logs. the first of error problems in the log was something to do with a unidentified user heres that errors:
Sun 24 Feb 2008 20:51:50 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Wed 27 Feb 2008 13:11:17 PST - Someone has tried to illegally access the GUS admin page. User id: , Username: , IP: 66.249.70.72
all errors prior to these and after are like these although the errors are constant after the above thre came about:
Wed 12 Mar 2008 10:58:34 PST - _BLOCK_TEMPLATE[glMenu] = blockheader-left.thtml,blockfooter-left.thtml
Wed 12 Mar 2008 10:58:34 PST - Block template for the footer of glMenu is: blockfooter-left.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[admin_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the header of admin_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[admin_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the footer of admin_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[user_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the header of user_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[user_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the footer of user_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[site_feeds] = blockheader-left.thtml,blockfooter-left.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the header of site_feeds is: blockheader-left.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[site_feeds] = blockheader-left.thtml,blockfooter-left.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the footer of site_feeds is: blockfooter-left.thtml
These errors show 2136 lines just today in my log. And the error log is 28.5mg & 281735 lines and all errors like the one's above.
Just out of curiosity if I did want to just renew the database with a backup do you need to drop all the tables first or will the new overlay?
alot of these errors are for the pro menu I would say about 20000 lines of my error log are from this menu
I appreciate your help jmucchiello
Thanks,
Dennis
Text Formatted Code
Thu 21 Feb 2008 00:50:38 PST - Someone has tried to illegally access the GUS admin page. User id: , Username: , IP: 66.249.70.198 Sun 24 Feb 2008 20:51:50 PST - [pear_error: message="mail() returned failure" code=0 mode=return level=notice prefix="" info=""]
Wed 27 Feb 2008 13:11:17 PST - Someone has tried to illegally access the GUS admin page. User id: , Username: , IP: 66.249.70.72
Text Formatted Code
Wed 12 Mar 2008 10:58:34 PST - Block template for the header of glMenu is: blockheader-left.thtml Wed 12 Mar 2008 10:58:34 PST - _BLOCK_TEMPLATE[glMenu] = blockheader-left.thtml,blockfooter-left.thtml
Wed 12 Mar 2008 10:58:34 PST - Block template for the footer of glMenu is: blockfooter-left.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[admin_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the header of admin_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[admin_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the footer of admin_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[user_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the header of user_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[user_block] = glmenu/cssmenu/blank.thtml,glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the footer of user_block is: glmenu/cssmenu/blank.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[site_feeds] = blockheader-left.thtml,blockfooter-left.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the header of site_feeds is: blockheader-left.thtml
Wed 12 Mar 2008 10:58:35 PST - _BLOCK_TEMPLATE[site_feeds] = blockheader-left.thtml,blockfooter-left.thtml
Wed 12 Mar 2008 10:58:35 PST - Block template for the footer of site_feeds is: blockfooter-left.thtml
6
8
Quote
All times are EDT. The time is now 09:55 pm.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content