Topic: Problems with SVSNICK (Read 14421 times)

lordwoodoo · « **on:** March 20, 2008, 07:03:44 PM »

hi!

im is a server admin in one irc network using unreal 3.2.7 and anope 1.7. all connections is ok and im is ADM in Staff os services...but...

When use: /os svsnick nick1 nick2

[13:02:50] -OperServ- Access Denied.

my services is ulined in unreal..all done!

Thanxs for help!

Jan Milants · « **Reply #1 on:** March 20, 2008, 07:39:18 PM »

depending on the settings off your network you may need to be /oper 'ed (and you need to have a global oline) and you must be identified to your nick.

Jobe · « **Reply #2 on:** March 20, 2008, 08:44:53 PM »

You will also have needed to do /os set superadmin on as well to be able to use SVSNICK

lordwoodoo · « **Reply #3 on:** March 20, 2008, 09:34:50 PM »

i set superadmin man and my nick is registered and identified....but dont work svsnick...

Jobe · « **Reply #4 on:** March 20, 2008, 10:00:03 PM »

Can you get a few pieces of information for us?

/msg OperServ staff
/msg NickServ info <yournick> all
/whois <yournick>

lordwoodoo · « **Reply #5 on:** March 20, 2008, 11:27:05 PM »

~Posseidon@Server-Admin.network.net
( Name ): Akula
( Channels ): #offtopic-portuguese &#admins
( IRCop ): is a IRC Admin
( Help ): EstÃ¡ disponÃvel para ajuda-lo
( Registered ): Nick registrado e identificado
( Server ): irc.Hub4Ever.Org Irc Hub4Ever Network
>>> End of Whois

[17:23:17] -OperServ- On NÃvel Nick
[17:23:18] -OperServ- * OPER clear-mode [kill]
[17:23:18] -OperServ- * OPER FreeSpirit [Dr_House]
[17:23:18] -OperServ- * OPER K4O5
[17:23:18] -OperServ- OPER Kakinho
[17:23:18] -OperServ- OPER MeTRaLHa
[17:23:18] -OperServ- OPER Pingo
[17:23:18] -OperServ- OPER SpiritS
[17:23:18] -OperServ- OPER the_best_boy
[17:23:18] -OperServ- * OPER wicked
[17:23:18] -OperServ- * ADMN [G]Prime
[17:23:18] -OperServ- ADMN Alex-Musicman
[17:23:18] -OperServ- ADMN Diabo
[17:23:18] -OperServ- ADMN Gwydion
[17:23:18] -OperServ- * ADMN Posseidon
[17:23:18] -OperServ- * ROOT Nyx

[17:24:01] -NickServ- Posseidon is Akula
[17:24:01] -NickServ- Posseidon is a Administrator of Services.
[17:24:01] -NickServ- Is online at: ~Posseidon@Server-Admin.network.net
[17:24:01] -NickServ- Time of register: 10 Fev 13:06:37 2008 UTC
[17:24:01] -NickServ- Last exit masage: Quit: changing servers
[17:24:01] -NickServ- E-mail: what@waht.com
[17:24:01] -NickServ- Options: Protect, Security, Private, Auto-op
[17:24:01] -NickServ- Expire at: 19 Abr 23:18:05 2008 UTC

Jobe · « **Reply #6 on:** March 21, 2008, 04:18:33 PM »

Which version of Anope are you using? Use "/quote version services.server.name" to find out

Jan Milants · « **Reply #7 on:** March 21, 2008, 05:19:50 PM »

did you do /os set superadmin on before trying to use svsnick ?

Jobe · « **Reply #8 on:** March 21, 2008, 06:02:57 PM »

Quote

Originally posted by Viper
did you do /os set superadmin on before trying to use svsnick ?

That was why I asked which version, as if he is using 1.7.21, then he wont be able to do that and consequently wont be able to use SVSNICK.

Kreon · « **Reply #9 on:** March 21, 2008, 11:02:20 PM »

Quote

Originally posted by Jobe1986
That was why I asked which version, as if he is using 1.7.21, then he wont be able to do that and consequently wont be able to use SVSNICK.

Why?
I'm using anope 1.7.21 with standard config-enabled option to get superadmin status, and that seems to work.

katsklaw · « **Reply #10 on:** March 21, 2008, 11:12:39 PM »

Quote

Originally posted by Kreon
Quote
Originally posted by Jobe1986
That was why I asked which version, as if he is using 1.7.21, then he wont be able to do that and consequently wont be able to use SVSNICK.

Why?
I'm using anope 1.7.21 with standard config-enabled option to get superadmin status, and that seems to work.

That's the point .. in 1.7.21 you must be ROOT to use any /os set command including superadmin .. which is required for SVSNICK.

so the thing is you simply don't have enough access to use SVSNICK .. please contact your Network Admin.

lordwoodoo · « **Reply #11 on:** March 22, 2008, 05:05:22 PM »

The most fun I get superadmin ... not only use svsnick. Just that

/os set superadmin on

[22:33:21]-OperServ-You are now a Super-Admin

/os svsnick teste1 test2

[22:35:27] -OperServ- Access Denied.

/os set superadmin off

[22:34:03]-OperServ- You is no longer a Super-Admin

Jan Milants · « **Reply #12 on:** March 22, 2008, 06:45:20 PM »

Quote

[22:35:27] -OperServ- Access Denied.

Quote

[22:34:03]-OperServ- You is no longer a Super-Admin

your timesptamps are off: you turned superadmin off before using svsnick...
and the very command sequence you entered works fine for me..

[Edited on 22-3-2008 by Viper]

lordwoodoo · « **Reply #13 on:** March 23, 2008, 01:14:24 PM »

/os set superadmin on
[18:42:24] -OperServ- You are now a Super-Admin

/os svsnick teste teste1
[18:43:05] -OperServ- Access Denied.

/os set superadmin off
[18:43:35] -OperServ- You is no longer a Super-Admin

Jobe · « **Reply #14 on:** March 23, 2008, 02:59:26 PM »

Can you try svsnick as a services root nick?

Can you additionally give us a list of ALL modules loaded using /msg OperServ modlist

[Edited on 23-3-2008 by Jobe1986]

Jan Milants · « **Reply #15 on:** March 23, 2008, 03:12:27 PM »

It is impossible to get that with stock anope...
SET SUPERADMIN has been restricted to Services Roots
and SVSNICK is restricted to Services Admins who are superadmin..

I m guessing you are using a module that affects the behaviour of anope then...
paste the reply of /os modlist..
and the reply of /os staff and /ns info <yournick> all again

and did you translate the reply of nickserv for us in your above posts because it doesn't match what nickserv would normally say in any language?

katsklaw · « **Reply #16 on:** March 23, 2008, 06:07:30 PM »

actually a more accurate list would be: /os modlist 3rd

lordwoodoo · « **Reply #17 on:** March 24, 2008, 03:28:52 PM »

[12:27:36] -OperServ- Lista de MÃ³dulos atual:
[12:27:36] -OperServ- MÃ³dulo: bs_restrict_kb [$Id: bs_restrict_kb.c v1.0.0 19-02-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: cs_count [$Id: cs_count.c v2.0.0 31-08-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: cs_droppass [$Id: cs_droppass.c v1.0.0 12-08-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: cs_unban [$Id: cs_unban.c v1.0.0 04-07-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: cs_appendtopic [$Id: cs_appendtopic.c 1332 2008-01-04 10:43:21Z geniusdex $] [Supported]
[12:27:36] -OperServ- MÃ³dulo: cs_enforce [$Id: cs_enforce.c 1335 2008-01-06 13:38:15Z geniusdex $] [Supported]
[12:27:36] -OperServ- MÃ³dulo: enc_none [$Id$] [Encryption]
[12:27:36] -OperServ- MÃ³dulo: hs_request [$Id$] [Supported]
[12:27:36] -OperServ- MÃ³dulo: ns_sidentify [$Id: ns_sidentify.c v1.0.0 25-08-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: ns_clist [$Id: ns_clist.c v2.0.0 30-07-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: ns_noexpire [$Id: ns_noexpire.c v1.0.1 23-01-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: ns_greetoper [$Id: ns_greetoper.c v1.0.0, 19-10-2006 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: ns_ajoin [4.2.0] [3rd]
[12:27:36] -OperServ- MÃ³dulo: ns_sagroup [1.0] [3rd]
[12:27:36] -OperServ- MÃ³dulo: ns_maxemail [$Id: ns_maxemail.c 1332 2008-01-04 10:43:21Z geniusdex $] [Supported]
[12:27:36] -OperServ- MÃ³dulo: os_root_superadmin [$Id: os_root_superadmin v1.0.0 13-04-2007 01:15PM n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: os_svsnick_sra [1.0.0-FINAL] [3rd]
[12:27:36] -OperServ- MÃ³dulo: os_shun [1.0] [3rd]
[12:27:36] -OperServ- MÃ³dulo: os_lastreg [$Id: os_lastreg.c v2.0.0 04-02-2008 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: os_forceid [$Id: os_forceid.c v1.0.1 12-01-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: os_extrainfo [$Id: os_extrainfo.c v2.0.0 20-08-2007 n00bie $] [3rd]
[12:27:36] -OperServ- MÃ³dulo: os_access_levels [2.2-FINAL] [3rd]
[12:27:36] -OperServ- MÃ³dulo: os_info [$Id: os_info.c 1332 2008-01-04 10:43:21Z geniusdex $] [Supported]
[12:27:36] -OperServ- MÃ³dulo: os_notinchanlist [2.3] [3rd]
[12:27:36] -OperServ- MÃ³dulo: unreal32 [$Id: unreal32.c 1291 2007-08-30 20:59:14Z drstein $] [Protocol]

Jan Milants · « **Reply #18 on:** March 24, 2008, 03:32:46 PM »

Quote

os_svsnick_sra [1.0.0-FINAL] [3rd]

what do you think that module does?
it restricts SVSNICK to services roots and drops the requirement of superadmin...
so obviously the root administrator of your network decided SA's (and you are one of them) shouldn't be granted access to SVSNICK

if your net uses that much modules you might consider asking your technical staff for support before asking us...

[Edited on 24-3-2008 by Viper]

katsklaw · « **Reply #19 on:** March 24, 2008, 09:22:33 PM »

I just tested this for a bug that I just closed as invalid. on Anope-1.7.21 without 3rd party modules, os SVSNICK requires Super-Admin, which is limited to ServicesRoot, NOT ServicesAdmins and everything works as predicted.

[17.17.15] -OperServ- Only Super-Admins can use this command.
[17.17.25] -OperServ- You are now a SuperAdmin
[17.17.26] [GlobOps] <OperServ> katsklaw is now a Super-Admin
[17.17.26] -OperServ- The nick katsklaw is now being changed to kats.
[17.17.27] [GlobOps] <OperServ> katsklaw used SVSNICK to change katsklaw to kats
[17.17.27] * katsklaw is now known as kats

Since os_svsnick_sra is my module, I can safely say there are no bug reports on it so far.In fact since you are only a servicesadmin and this module is loaded, that means it's working perfectly as that module is designed for svsnick to be only used by root, hence it's name os_SVSNICK_SRA.

Additionally, you have a module conflict.

If you use 1.7.20 or higher you do not need: os_root_superadmin

On top of that, since you use my os_access_levels module you do not need os_root_superadmin because my module handles that already.

I'd also like to point out that while the Anope team is here to help with questions, this specific question should have been directed at a root admin on your network and if they needed help then they should come to us. As it is you lack sufficient access for any trouble shooting that may come up. Which is why I originally told you days ago to talk to your admin. You just wasted everyones time.

[Edited on 24-3-2008 by katsklaw]

lordwoodoo · « **Reply #20 on:** March 25, 2008, 04:02:40 PM »

thanxs for help to all......and sory for problems....im is response for services in network katsklaw and sory for problems...

News:

Author Topic: Problems with SVSNICK (Read 14421 times)

katsklaw

katsklaw

katsklaw