Print

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

[MadMe200]

Hi i just updated Anope from window to hub but when it connets it removes Nick Modes

Nick sets mode: +ao Nick Nick
Nick sets mode: +oq Nick Nick
Nick sets mode: +v Nick
Nick sets mode: +oa Nick Nick
Nick sets mode: +oa Nick Nick
Nick sets mode: +oa Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick
Nick sets mode: -ahoq Nick Nick Nick

and i was wondering what is the problem

[Jobe]

Is Nick a BotServ bot at all?

[deiks]

Is Nick a BotServ bot at all?

or don't have access on that channel if Nick is not BotServ bot ..

[MadMe200]

Yes BotServNick sets mode: -ahoq UserNick UserNick UserNick

[deiks]

Yes BotServNick sets mode: -ahoq UserNick UserNick UserNick

Then 1st Nick is not same as 2nd and 3rd in this operation :]
So try adding access for deoped nick, or if it is your nick, try /msg OperServ set superadmin on

[MadMe200]

Nope still does it

[Thu-14:23] * shithead (itsme@ductnet.kicks-ass.org) has joined #test
[Thu-14:23] * shithead sets mode: +ao shithead shithead
[Thu-14:23] * shithead sets mode: +oq DUCT_TAPE DUCT_TAPE
[Thu-14:23] * shithead sets mode: +v Prince-albert
[Thu-14:23] * shithead sets mode: +oa Country|Rocker Country|Rocker
[Thu-14:23] * shithead sets mode: -ahoq IRC-COP IRC-COP IRC-COP IRC-COP
[Thu-14:23] * shithead sets mode: -ahoq IRC-COP IRC-COP IRC-COP IRC-COP

[deiks]

And who is now IRC-COP, coz I don't see that is IRC-COP opped here..

[MadMe200]

IRC-COP is a bot (Not BotServ) shithead is the BotServ Bot

[deiks]

Then check does IRC-COP have access on #test channel.
When secureops option is enabled only users with access at channel can be opped

[MadMe200]

All of us have access to the channel

ChanServ Access list for #test:
ChanServ 19 SOP IRC-COP

[deiks]

Hm... Then just check is IRC-COP bot identified to services.

Or do u have some module installed that screws all thing

Or it is really bug, so try 1.7.* branch.

DBases are same, just make new conf via example.conf file

[katsklaw]

the most common cause is a TS desync, either the channel is out of sync on 1 or more servers or your servers have in correct timestamps.

[Kanegasi]

I've ran across this problem as well. I installed NeoStats, and when one of the bots from stats joins, chanserv (or in this case an anope bot with symbiosis) immediately -ahoq's him after he ops himself. I can go in and op him back and the services don't take that away. Is there a way to fix this TS error? I was thinking of finding a few TS servers and using the Unreal sync option in the .conf file. Any suggestions?

EDIT: stats is ulined btw

[deiks]

If that is all problem, use /msg ChanServ set #channel secureops off
In that case, Anope is correct, and without error

[katsklaw]

I've ran across this problem as well. I installed NeoStats, and when one of the bots from stats joins, chanserv (or in this case an anope bot with symbiosis) immediately -ahoq's him after he ops himself. I can go in and op him back and the services don't take that away. Is there a way to fix this TS error? I was thinking of finding a few TS servers and using the Unreal sync option in the .conf file. Any suggestions?

EDIT: stats is ulined btw

See: http://forum.anope.org/index.php?topic=454.0