gm.cgi: Use of uninitialized value

[squeezer]

I'm running greymatter 1.7.2 on a Fedora Core 6 Linux server on Apache 2.2.3. I am getting an error. I can login fine. Upgraded from 1.7.1 so I attempted to rebuild everything, but I get this error:

Software error:

An internal error has occured
and the administrators have been notified.

For help, please send mail to the webmaster ([e-mail]), giving this error message and the time and date of the error.

and when i look at apache's error_log:

[Sat Mar 17 19:52:15 2007] [error] [client 68.209.223.242] [Sat Mar 17 19:52:15 2007] gm.cgi: Use of uninitialized value in substitution (s///) at libs/Gm_Utils.pm line 348., referer: www.stephaniediane.com/
[Sat Mar 17 19:52:15 2007] [error] [client 68.209.223.242] [Sat Mar 17 19:52:15 2007] gm.cgi: Use of uninitialized value in pattern match (m//) at libs/Gm_Utils.pm line 349., referer: www.stephaniediane.com/
[Sat Mar 17 19:52:15 2007] [error] [client 68.209.223.242] [Sat Mar 17 19:52:15 2007] gm.cgi: An internal error has occured , referer: www.stephaniediane.com/
[Sat Mar 17 19:52:15 2007] [error] [client 68.209.223.242] [Sat Mar 17 19:52:15 2007] gm.cgi: and the administrators have been notified., referer: www.stephaniediane.com/

perl version info:

perl-DBD-AnyData-0.08-3.fc6
perl-DBD-MySQL-3.0007-1.fc6
perl-HTML-Tagset-3.10-2.1.1
perl-DBI-1.52-1.fc6
perl-5.8.8-10
perl-Text-CSV_XS-0.23-5.fc6
perl-XML-Parser-2.34-6.1.2.2.1
perl-AnyData-0.10-3.fc6
perl-DBD-SQLite-1.12-2.fc6
perl-DBD-XBase-0.241-5.fc6
perl-DBD-SQLite2-0.33-6.fc6
perl-HTML-Parser-3.55-1.fc6
perl-Compress-Zlib-1.42-1.fc6
perl-URI-1.35-3
perl-XML-Twig-3.26-1.fc6
perl-DBD-Pg-1.49-1.fc6
perl-DBD-CSV-0.22-5.fc6



any suggestions?

[coldstone]

Are you able to do 'Diagnositics and Repair'? Also, after you upgraded, did you save the new configurations?

It looks like it doesn't like a entry number that is passed in to make it into a filename, since GM will take entry 1 and make it 00000001.html.

[squeezer]

I get the same error when I do the diagnostics and repair, and yes I did save the configuration.

[coldstone]

Hmm, thats not good then. Did your paths change at all? Also, when you upgraded, did you move any of your data files around?

Can you chmod your gm-templates.cgi file to something other than 666 and see if Diagnostic and Repair complains? I am trying to see how far GM gets before it errors out.

[squeezer]

coldstone said:

Hmm, thats not good then. Did your paths change at all? Also, when you upgraded, did you move any of your data files around?

Can you chmod your gm-templates.cgi file to something other than 666 and see if Diagnostic and Repair complains? I am trying to see how far GM gets before it errors out.

when i log in after changing gm-templates permissions to 000:

Content-type: text/html

greymatter 1.7.2
Error Notice

gm-templates.cgi is not readable. Please check the file permissions and make sure you CHMOD it to 666.

v1.7.2 · ©2000-2006 The Greymatter Team

[coldstone]

Grr, thats right, it'll check on login to. If you get to the Config Screen, just before clicking diagnositics and repair, _then_ chmod the file, we can see how far its getting.

Also, how many entries do you have?

[squeezer]

same error when i click diagnostics and repair:

Error Notice

gm-templates.cgi is not writable. Please check the file permissions and make sure you CHMOD it to 666.

there are 19 entries on the site according to the archives directory.

[coldstone]

Ok, that means its getting past that part before having issues. You don't happen to have a 00000000.cgi file in your archives directory do you?

I think to figure this out I will need to create a file that will put stuff into the log, so we can see where precisely it's having trouble. I will have this ready in a day or two.

[petefinnigan]

Hi Coldstone,

Could we can use Gm_Trace.pm for this?

cheers

Pete

[coldstone]

Eventually, yeah Gm_Trace will be perfect for this. I just wanted to whip up something quick.

[coldstone]

Squeezer,

I uploaded a gm-libary-172-trace.zip to the 50megs.com page. Please download this, try to do a 'Diagnostics and repair' and post the log output (not all of it, it its excessively long, just the 20 lines before it stops.

Lastly, a thought occurred to me, do you have a server offset value?