random blank pages

CentOS 4.4
spamassassin 3.1.7
postfix 2.2.10-1-RHEL4.2
httpd-2.0.52-28.ent.centos4
php-4.3.9-3.22
pear 1.5.0

I have a new server setup using the 'trunk' version of Maia.
(I have 
also tried the 1.0.2 tarball with the same results.) Both of
the 
configtest.pl and the configtest.php files run and show all
is OK. But 
"random" pages display blank. I say
"random" because I have not found a 
pattern yet. The only thing I can find is in the
httpd/error_log file I 
see this message whenever I get a blank page.

PHP Fatal error:  Call to undefined function:  fetchrow() in

/var/www/html/maia/settings.php on line 633, referer: 
http://192.168.1
.3/maia/admindex.php

The .php file it is in is different. I have seen
"settings.php" and 
"domainsettings.php" and
"adminindex.php" but mostly it is the 
"settings.php" file.


- Gary

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Feb 20, 2007, at 10:21 AM, Gary MacKay wrote:
>
> I have a new server setup using the 'trunk' version of
Maia. (I have
> also tried the 1.0.2 tarball with the same results.)
Both of the

First of all, don't do that, unless you are wanting to help 

develop.   Trunk is unstable now,  not even alpha quality. 
The  
stable maintenance branch is now branches/1.0


> configtest.pl and the configtest.php files run and show
all is OK. But
> "random" pages display blank. I say
"random" because I have not  
> found a
> pattern yet. The only thing I can find is in the
httpd/error_log  
> file I
> see this message whenever I get a blank page.
>
> PHP Fatal error:  Call to undefined function: 
fetchrow() in
> /var/www/html/maia/settings.php on line 633, referer:
> http://192.168.1
.3/maia/admindex.php

That usually happens when a sql query didn't work right, bad
SQL and  
such, or maybe if the mysql server went away.   If you are
have  
mismatched schemas from trunk to 1.0.2, you could get this
easy.  (I  
don't think trunk's schema is up to date with the changes
yet)

Wipe your database, download 1.0.2 or branches/1.0, and
re-init the  
DB... (this isn't a live DB yet, right?)



David Morton
Maia Mailguard http://www.maiamailguard
.com
mortondadgrmm.net



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF2y5bUy30ODPkzl0RAq1nAKDIpfVn2gfCGi9xQv3mSVA1/gIbDQCg
uUmT
WsrLsXSr5Kbkrl8+wQIpPT8=
=lRH0
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

David Morton wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Feb 20, 2007, at 10:21 AM, Gary MacKay wrote:
>>
>> I have a new server setup using the 'trunk' version
of Maia. (I have
>> also tried the 1.0.2 tarball with the same
results.) Both of the
>
> First of all, don't do that, unless you are wanting to
help develop.   
> Trunk is unstable now,  not even alpha quality.  The
stable 
> maintenance branch is now branches/1.0
>
>
>> configtest.pl and the configtest.php files run and
show all is OK. But
>> "random" pages display blank. I say
"random" because I have not found a
>> pattern yet. The only thing I can find is in the
httpd/error_log file I
>> see this message whenever I get a blank page.
>>
>> PHP Fatal error:  Call to undefined function: 
fetchrow() in
>> /var/www/html/maia/settings.php on line 633,
referer:
>> http://192.168.1
.3/maia/admindex.php
>
> That usually happens when a sql query didn't work
right, bad SQL and 
> such, or maybe if the mysql server went away.   If you
are have 
> mismatched schemas from trunk to 1.0.2, you could get
this easy.  (I 
> don't think trunk's schema is up to date with the
changes yet)
>
> Wipe your database, download 1.0.2 or branches/1.0, and
re-init the 
> DB... (this isn't a live DB yet, right?)
>
>
>
> David Morton
> Maia Mailguard http://www.maiamailguard
.com
> mortondadgrmm.net
>
Well, um, err, yeah. It is a live system. In the past I
guess I have 
been lucky. I have used the trunk version with no problems.
I did not 
give it a thought when I setup this new one. I don't suppose
there is 
any way to salvage the data?

- Gary

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Feb 20, 2007, at 11:57 AM, Gary MacKay wrote:
>
> Well, um, err, yeah. It is a live system. In the past I
guess I  
> have been lucky. I have used the trunk version with no
problems. I  
> did not give it a thought when I setup this new one. I
don't  
> suppose there is any way to salvage the data?

Ouch.   Ok, did you run the upgrade script with the recent
trunk?    
If so, then you would probably be better off staying.  I
*think* it's  
reletively stable, I'm using it on my own system, but no  
guarantees.   You would then want to reset stats.   
However, given  
your errors, I don't think you did.

If not, revert  the scripts and all back to the 1.0 branch. 
 Any  
data that came in with a trunk amavisd-maia may be lost(or
present  
but with incorrect user ids linked), and I'm not sure how
scrambled  
it may be.  It may be ok, if you don't have a lot of aliased
 
accounts... but OTOH, you may have people's email linked to
the wrong  
accounts. You better log in as some other users and see

If you did not upgrade or run the new amavisd-maia in trunk,
and did  
not run the upgrade script, then you are ok.

(Shouting in the subject line to hopefully get people's
attention.  I  
announced this several times, and the web page says it's
bleeding  
edge.... but there's always someone who misses the
announcement.   : 
(   )

The big change so far in trunk is a change to per-address
stats and  
settings, outlined in http://www.ma
iamailguard.org/maia/wiki/ 
PerEmailStats

avid Morton
Maia Mailguard http://www.maiamailguard
.com
mortondadgrmm.net



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF2z63Uy30ODPkzl0RAvcWAJ4/WXk9wFfnPnA6L/sUHKp8KRpzEwCg
ij5F
HsJ6+zEYslMS21zCtxI8b/8=
=Vwqi
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

David Morton wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Feb 20, 2007, at 11:57 AM, Gary MacKay wrote:
>>
>> Well, um, err, yeah. It is a live system. In the
past I guess I have 
>> been lucky. I have used the trunk version with no
problems. I did not 
>> give it a thought when I setup this new one. I
don't suppose there is 
>> any way to salvage the data?
>
> Ouch.   Ok, did you run the upgrade script with the
recent trunk?   If 
> so, then you would probably be better off staying.  I
*think* it's 
> reletively stable, I'm using it on my own system, but
no guarantees.   
> You would then want to reset stats.    However, given
your errors, I 
> don't think you did.
>
> If not, revert  the scripts and all back to the 1.0
branch.   Any data 
> that came in with a trunk amavisd-maia may be lost(or
present but with 
> incorrect user ids linked), and I'm not sure how
scrambled it may be.  
> It may be ok, if you don't have a lot of aliased
accounts... but OTOH, 
> you may have people's email linked to the wrong
accounts. You better 
> log in as some other users and see
>
> If you did not upgrade or run the new amavisd-maia in
trunk, and did 
> not run the upgrade script, then you are ok.
>
> (Shouting in the subject line to hopefully get people's
attention.  I 
> announced this several times, and the web page says
it's bleeding 
> edge.... but there's always someone who misses the
announcement.   :(   )
>
> The big change so far in trunk is a change to
per-address stats and 
> settings, outlined in 
> 
http://www.maiamailguard.org/maia/wiki/PerEmailStats
>
> David Morton
> Maia Mailguard http://www.maiamailguard
.com
> mortondadgrmm.net
>
I am truly sorry I missed that. I have set up so many of
these boxes for 
my clients that I kind of have a system down and just
blindly fly along 
some times. Very ashamed to be one of those people that are
so 
aggravating  to others because they do not take time to
read!   grr....

Anyway, it appears from what I can see, that I did run the
upgrade.php 
file. It looks like I am running everything in trunk
"execpt" the 
amavis-maia file. Not sure how I missed that one during the

install/upgrade.

This box is just a filter and passes it on to an Exchange
Server. It has 
only been running a couple of weeks. What harm would there
be in just 
nuking the db as you suggested and restarting it??

- Gary

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Feb 20, 2007, at 12:49 PM, Gary MacKay wrote:
> I am truly sorry I missed that. I have set up so many
of these  
> boxes for my clients that I kind of have a system down
and just  
> blindly fly along some times. Very ashamed to be one of
those  
> people that are so aggravating  to others because they
do not take  
> time to read!   grr....
>

It happens. 


> Anyway, it appears from what I can see, that I did run
the  
> upgrade.php file. It looks like I am running everything
in trunk  
> "execpt" the amavis-maia file. Not sure how I
missed that one  
> during the install/upgrade.
>

hrm.   I don't know what that would do.


> This box is just a filter and passes it on to an
Exchange Server.  
> It has only been running a couple of weeks. What harm
would there  
> be in just nuking the db as you suggested and
restarting it??

I think that would be the best.

The risks of wiping:  losing a false positive, annoying
users with  
setting up Maia accounts again.
The risks of not wiping: errors, mismatched emails

If you want to use svn, use https://www.maiama
ilguard.com/svn/ 
branches/1.0 and you'll have the latest and greatest stable.




David Morton
Maia Mailguard http://www.maiamailguard
.com
mortondadgrmm.net



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFF20vDUy30ODPkzl0RAk/ZAKDEBhx9wEBrEv+qVMc/sjf/b8XLAQCg
tAjI
sh80TsN/RJNVpvD+rXxK5pA=
=dGZE
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users