Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DaZa]

One of my IRCops picked this up this morning, not sure if this is since 1.7.18 or has been there for awhile.

All registered nicknames show up as a Services Root Administrator when you do a /msg NickServ INFO

For example:
-NickServ- Play-Mate is Hugh Hefner is my man....
-NickServ- Play-Mate is a services root administrator.
-NickServ- Play-Mate is currently online.
-NickServ-   Time registered: Oct 01 20:44:30 2005 EST

However the nickname is NOT defined as a services root nickname nor does it actually have that access with OperServ.

I'm using Anope 1.7.18 currently running on Debian Stable and using MySQL with Anope.

Any ideas whats gone wrong?

[Jan Milants]

can't duplicate on 1.7.18...

no sql though...

[Edited on 4-1-2007 by Viper]

[katsklaw]

cann not duplicate on 1.7.18 with sql.

Please reply with the output of: /os modlist

[DaZa]

Originally posted by katsklaw
cann not duplicate on 1.7.18 with sql.

Please reply with the output of: /os modlist

This is what I get:

-OperServ- Current Module list:
-OperServ- Module: cs_appendtopic [$Id: cs_appendtopic.c 1122 2006-08-06 15:00:13Z certus $] [Supported]
-OperServ- Module: cs_enforce [$Id: cs_enforce.c 957 2006-01-24 07:54:48Z certus $] [Supported]
-OperServ- Module: enc_none [$Id$] [Encryption]
-OperServ- Module: hs_request [$Id$] [Supported]
-OperServ- Module: ircd_wallonreg [2.1] [3rd]
-OperServ- Module: ns_maxemail [$Id: ns_maxemail.c 953 2006-01-14 11:36:29Z certus $] [Supported]
-OperServ- Module: os_tssync [1.0] [3rd]
-OperServ- Module: os_info [$Id: os_info.c 1162 2006-09-29 17:54:07Z geniusdex $] [Supported]
-OperServ- Module: unreal32 [$Id: unreal32.c 1185 2006-10-17 20:42:40Z rob $] [Protocol]
-OperServ- 9 Modules loaded.

Only 2 modules I use besides what comes with anope is os_tssync and ircd_wallonreg

I've got no idea why its showing this.

[katsklaw]

me neither. Try restarting services and see if it fixes the issue.

[DaZa]

Originally posted by katsklaw
me neither. Try restarting services and see if it fixes the issue.

Nope problem is still there after a reboot of services.

Might try going back to 1.7.17 and see if it makes a difference.

[DaZa]

Originally posted by katsklaw
me neither. Try restarting services and see if it fixes the issue.

Tried a reboot, no luck.

Downgraded to 1.7.17 and the problem is gone.

Must be something in SQL thats gone screwy, think I'll wait till a 1.7.19 before I switch back.

Had enough fun with 1.7.16 with its problems!

[Jan Milants]

Originally posted by DaZa
Must be something in SQL thats gone screwy, think I'll wait till a 1.7.19 before I switch back.

if something went wrong with sql, it would most likely have happened when updating the database structure when going from .17 to .18 and since .19 will use the same database as .18, or even with more changes, i doubt waiting will solve your problem...

i m also not sure whether .17 will work properly with a database structure of .18 ... did you roll back your database as well ?

[DaZa]

Originally posted by Viper

Originally posted by DaZa
Must be something in SQL thats gone screwy, think I'll wait till a 1.7.19 before I switch back.

if something went wrong with sql, it would most likely have happened when updating the database structure when going from .17 to .18 and since .19 will use the same database as .18, or even with more changes, i doubt waiting will solve your problem...

i m also not sure whether .17 will work properly with a database structure of .18 ... did you roll back your database as well ?

Yep I did a SQL backup of the tables before I did the upgrade so I reverted back to .17 table structure.

I'm going to try katsklaws suggestion via bug tracker to install .18 to a clean sql database and populate from local db files and see what happens.