| View previous topic :: View next topic |
| Author |
Message |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Fri Sep 10, 2004 5:31 am Post subject: Server says bot's nick is invalid |
|
|
| Quote: |
[02:26] Trying server broadway.ny.us.dal.net:6669
[02:26] DNS resolved broadway.ny.us.dal.net to 194.68.45.50
[02:26] net: connect! sock 7
[02:26] Connected to broadway.ny.us.dal.net
[02:26] -NOTICE- *** Looking up your hostname...
[02:26] -NOTICE- *** Found your hostname, cached
[02:26] -NOTICE- *** Checking Ident
[02:26] -NOTICE- *** Got Ident response
[02:26] Server says my nickname is invalid.
|
What could this possibly mean?
This is the result shown by: ./eggdrop -n asskicker.conf
My bots nick is: asskicker
and userident is: elite (shell username)
What could be the problem here?
I've tried many different client servers, still the same! _________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
Alchera Revered One

Joined: 11 Aug 2003 Posts: 3344 Location: Ballarat Victoria, Australia
|
Posted: Fri Sep 10, 2004 10:09 am Post subject: |
|
|
The nick you have chosen is probably Q:lined. _________________ Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
 |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Fri Sep 10, 2004 1:11 pm Post subject: |
|
|
I hope not, its on DALnet Alchera... or I will screw the staff, heh. A few days ago it was working, leme connect a client with the same nick and ident to DALnet's client server and check, whats the reason.  _________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Fri Sep 10, 2004 1:16 pm Post subject: |
|
|
WHOA... check this out
| Code: |
* Connecting to mesra.kl.my.dal.net (7000)
-
-mesra.kl.my.dal.net- *** Looking up your hostname...
-
-mesra.kl.my.dal.net- *** Checking Ident
-
* Identd request from 61.6.39.100
* Identd replied: 1287, 7000 : USERID : UNIX : elite
-
-mesra.kl.my.dal.net- *** Got Ident response
-
-mesra.kl.my.dal.net- *** Found your hostname
-
asskicker The nick asskicker is currently being held by a Services Enforcer. If you are the nicks owner, use /msg NickServ@services.dal.net RELEASE asskicker password to release the nickname. If the nickname recently expired, please wait patiently and try again later. [asskicker]
-
asskicker The nick asskicker is currently being held by a Services Enforcer. If you are the nicks owner, use /msg NickServ@services.dal.net RELEASE asskicker password to release the nickname. If the nickname recently expired, please wait patiently and try again later. [asskicker]
-
Closing Link: 0.0.0.0 (Ping timeout)
-
* Disconnected
-
* Connect retry #1 hotspeed.sg.as.dal.net (6666)
-
|
And on my client side
| Code: |
-
asskicker No such nick/channel
-
asskicker End of /WHOIS list.
-
|
They've really fiddled with the IRCd and screwed it up bigtime now!
| Quote: |
* Now talking in #dalnethelp
* Topic is '|Services: Here| The Official DALnet Services Help Channel. For IRCop help, join #OperHelp. Ask all questions in channel. No flooding/repeats/caps/control codes/ pastes. Want to help? Visit http://help.dal.net/dnh/policy.php. If you have ENFORCE problems releasing your nick, use RECOVER then RELEASE.'
* Set by PJKevin on Thu Sep 09 09:24:09
|
_________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
Alchera Revered One

Joined: 11 Aug 2003 Posts: 3344 Location: Ballarat Victoria, Australia
|
Posted: Fri Sep 10, 2004 7:01 pm Post subject: |
|
|
Someone's done something allright. LOL
You've got enforce set but it doesn't stop them trying.
Services Enforcer is a pain, it's been known to hang onto a nick for up to 10 minutes. Basically awyeah it was just bad timing on your part (or theirs). LOL _________________ Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
 |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Sat Sep 11, 2004 3:49 am Post subject: |
|
|
Nah there's a bug in services or bahamut itself.
I'll give you the link go and read about it!
http://www.freewebs.com/zehrila/dalnet/services/changes.html _________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
Alchera Revered One

Joined: 11 Aug 2003 Posts: 3344 Location: Ballarat Victoria, Australia
|
Posted: Sat Sep 11, 2004 5:22 pm Post subject: |
|
|
An interesting read. I think 12 hours is just a little excessive. The one nick I really guard against being used is ghosted whenever I'm the one not using it which probably explains why I haven't come across this new Enforcer setting yet.  _________________ Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
 |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Sun Sep 12, 2004 5:54 am Post subject: |
|
|
Look at it this way Alchera. Now I would have to develop a tcl to bind on that raw msg or server notice to release the enforcer? Because this is happening alot to my bots when they lag or services do.
Hmm but isn't this crap. You can't conneect untill it is realeased. Moreover how will the bot release it, with its atlnick? I guess then we would have to make a solution for that.  _________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
Alchera Revered One

Joined: 11 Aug 2003 Posts: 3344 Location: Ballarat Victoria, Australia
|
Posted: Mon Sep 13, 2004 5:51 pm Post subject: |
|
|
Just had the same thing happen to a bot of mine today. We manually released it using only /ns release <botnick> [pass]. This happened after the bot timed out from mesra. Under normal circumstances the bot should have reconnected using it's alt nick (identifies to it's main nick) and reclaimed when free. _________________ Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
 |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Mon Sep 13, 2004 9:39 pm Post subject: |
|
|
Yeah this is really crap. I and a few other users are atleast trying to convince the coders to add a command to release the with nickserv maybe when it says that the nick is on enforcer.
This will atleast get bots to release their nicks via scripts and owners wouldn't have to do it manually, by their clients. My bot aswell didn't change to its altnick, instead it got the message for enforcer and got disconnected and it couldn't connect, I telnetted to it and found this out. _________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
Alchera Revered One

Joined: 11 Aug 2003 Posts: 3344 Location: Ballarat Victoria, Australia
|
Posted: Mon Sep 13, 2004 10:47 pm Post subject: |
|
|
Have fun with the coders. LOL
Allah Hafiz  _________________ Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
 |
Dedan Master

Joined: 09 Jul 2003 Posts: 260 Location: Memphis
|
Posted: Wed Sep 22, 2004 11:04 am Post subject: |
|
|
ok, i am having the same problem,
what i need is the bind for
" Server says my nickname is invalid."
then i can work from there.
i made this and it worked once,
but now it is not working, the server
will not allow the bot to get on dalnet
to execute the script:
| Code: |
bind raw -|- 432 Nserv:need:release
proc Nserv:need:release {from keyword text} {
global botnick iNickServ i_nick i_pass i_gost_timer i_timer
if {[string match -nocase "*$iNickServ*" "$text"]} {
if {[string match -nocase "*$i_nick*" "$text"]} {
putserv "PRIVMSG NickServ@services.dal.net :RELEASE $i_nick $i_pass"
}
}
}
|
so, if i can get the bind for
" Server says my nickname is invalid."
i will write the code.
hmmm, _________________ I once was an intelligent young man, now i am old and i can not remember who i was. |
|
| Back to top |
|
 |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Wed Sep 22, 2004 9:16 pm Post subject: |
|
|
What you can do here is directly bind to the raw number as you have done, 432 if its correct or string match the $arg or $text var.
| Quote: |
This is the raw and not 'Server say nick is invalid.' You will need to match for the following text:
The nick asskicker is currently being held by a Services Enforcer. If you are the nicks owner, use /msg NickServ@services.dal.net RELEASE asskicker password to release the nickname. If the nickname recently expired, please wait patiently and try again later. [asskicker]
|
| Code: |
bind raw - 432 nickserv:release
proc nickserv:release {from keyword arg} {
global botnick nickpass nick altnick
putquick "NICK $altnick" -next
#putquick "NICK $nick[rand 10][rand 10]" #for alternative nick
puthelp "PRIVMSG NickServ@services.dal.net :RELEASE $nick $nickpass"
return 0
}
or
bind raw - * nickserv:release
proc nickserv:release {from keyword arg} {
global botnick nickpass nick altnick
if {([string match "*The nick * is currently being held by a Services Enforcer. If you are the nicks owner*" $arg])} {
putquick "NICK $altnick" -next
#putquick "NICK $nick[rand 10][rand 10]" #for alternative nick
puthelp "PRIVMSG NickServ@services.dal.net :RELEASE $nick $nickpass"
return 0
}
}
|
Note: I used puthelp for the delay in releasing the nick after you are connected and putquick -next for the nick change when you are connecting, which might solve it, if possible.
The thing is, mostly it doesn't let you kill the enforcer or release the nick when it gives you the raw message. You have to switch to an alternative nick, then bind init-server or something then go ahead and release that nick after you have connected to the server, not while you are connecting to it or when it is giving you that error message.
You cannot release the nick enforcer when it gives you that error message, and that is really crappy I say, the coders should atleast let people release it when they get the error while connecting.
The thing is that you are not fully connected to the client server, hence you cannot message nickserv to release your nick while you get that message. Untill you are fully connected then only you can. _________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
Bingooss Voice
Joined: 19 Sep 2004 Posts: 11
|
Posted: Wed Sep 22, 2004 10:25 pm Post subject: |
|
|
hi Awyeah !
well just set off the enforced option for your bot nick (asskicker), manually release the nick by using
/nickserv release nick password
and set the enforced option off
and then try it will work , it worked for me too
BYE
ALI  |
|
| Back to top |
|
 |
awyeah Revered One

Joined: 26 Apr 2004 Posts: 1580 Location: Switzerland
|
Posted: Wed Sep 22, 2004 11:04 pm Post subject: |
|
|
I know that but there must be a solution around it. Setting enforce off, would hold the bots nick if some one is using it, suppose some one was using it before I loaded the bot, or some one got it through a netsplit and a collison occured or the bot was lagging and didn't identify to it, or the bot couldnt change its nick because it was not opped on an +R, +M chan. There are so many cases!
I would have to make a tcl script for that too, if some one else is using the bot's nick and $botname does not match the bots user@host, and if it is not an enforcer, then use the nickserv ghost command to ghost the nick to make it regain its nick back, $nick. _________________ ·awyeah·
==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
================================== |
|
| Back to top |
|
 |
|