"not found in config" errors after upgrade

[lionpanthera]

I kinda upgraded teleirc accidentally, at which point it exploded and stopped working. I hunted around the issues and found out about "--upgrade-config" so I did that and swapped in the new config.

But both before and after the upgrade config I'm getting these errors repeatedly:

error: channel AUTH not found in config!
error: channel RoboLion not found in config!

RoboLion is the name of the bot and should not be a channel. I have no idea what AUTH is. Any hints?

[FruitieX]

Hmm that's a generic (and frankly, stupid) error message we have for any sender (channel or query) that the bot does not know about. AUTH is probably some bot that your IRC server hosts for authenticating your nick (often this is optional, depends on the server),

As to why things broke, that's weird. Please post a version of your new config with any secrets (passwords, nicknames, irc servers) censored out, let's see if there's anything wrong there.

Disclaimer: I haven't touched this project in ages, unfortunately :(
Just haven't used IRC much lately.

[lionpanthera]

OK well I've poked at it some more and realized that it's less broken that I thought. (Though I apologize for the massively useful bug report of "stopped working". How useful.)

It's still joining IRC, but it's only joining one of the three configured IRC channels. In the channel that it joins, it seems to still work fine. So the problem is that it's not joining the other two channels.

I've attached a censored config.js.

config.js.txt

[steadfasterX]

I'm really not sure if thats related but I freshly installed teleirc today and I'm not able to get it connected to freenode IRC..
I'm new to teleirc and really would enjoy that software..

This is the output when writing something in the linked TG group:

~$ teleirc -vvv
info: using config file from: /home/sediadm/.teleirc/config.js
info: forcing log level to "silly"
error: channel * not found in config!
error: channel * not found in config!
error: channel * not found in config!
error: channel * not found in config!
debug: got tg msg: 
{ message_id: 13,
  from: 
   { id: xxxxxxxx,
     is_bot: false,
     first_name: 'xxxxxxxx',
     username: 'xxxxxxxx',
     language_code: 'xxxxxxxx' },
  chat: 
   { id: -xxxxxxxx,
     title: 'tgsfxtest',
     type: 'group',
     all_members_are_administrators: true },
  date: 1525878819,
  text: 'this text line is send from TG to the mapped group!' }
info: storing chat ID: -xxxxxxxx
info: successfully stored chat ID in /xxxxxxxx/.teleirc/tgsfxtest.chatid
verbose: << relaying to IRC: <09xxxxxxxx> this text line is send from TG to the mapped group!

so the TG connection seems to work properly but as said it can't join my IRC channels. Unfortunately there are no debug messages regarding the IRC join so its hard to track where the issue is..

config.js.txt

I have attached my config here too ^^

Any help greatly appreciated ..

EDIT
This has been tested and makes no difference at all:

• sasl: false & using the non encrypt irc port
• using an IRC chan without pass

[Mikaela]

@steadfasterX The only thing I can spot is that you have sasl: true without password: password in config.ircOptions https://github.com/FruitieX/teleirc/wiki/Identifying-to-NickServ#sasl-plain .

[steadfasterX]

Yea I tested with and without - without any difference. I'm just wondering about channel * .. Any way to debug the IRC connection?

[lionpanthera]

Apparently the problem was not with teleirc. I moved it to a different IRC server on the same network and now it's totally fine.

So... sorry. :)

[Mikaela]

Hmm that's a generic (and frankly, stupid) error message we have for any sender (channel or query) that the bot does not know about. AUTH is probably some bot that your IRC server hosts for authenticating your nick (often this is optional, depends on the server),

Reopening as this keeps confusing everyone new.

[lindhe]

Is there a good reason for having this message on loglevel error rather than, say, info?

[FruitieX]

info would probably be better suited here.

I'm not sure if there was any reasoning behind the current way, other than if running teleirc in the usual configuration with only one irc channel, a typo in that channel name would actually be a critical error.