TIMEOUT I'm using version 2.6.13 #302

wind-hx · 2022-04-20T03:12:27Z

Version 2.6.13 the same problem occurs, A large number of timeouts will occur in the program running for a long time, which will eventually lead to 100% of the CPU and the server cannot be used.

wind-hx · 2022-04-20T09:55:39Z

cpu-profile-6942-20220420-174229.cpuprofile.zip
This is the result of node.js cpu analysis

painor · 2022-04-20T16:35:05Z

is that the only code you're using? can you send a small reproducible code ?

wind-hx · 2022-04-21T04:12:34Z

is that the only code you're using? can you send a small reproducible code ?

Sorry, I can't reproduce this problem locally, but I can provide a development environment server, you can connect to the development environment server to view this error

wind-hx · 2022-04-21T04:34:16Z

is that the only code you're using? can you send a small reproducible code ?

This problem has been bothering me for a long time, I hope you can provide telegram contact information, I will send you the ip of the development environment server, you can connect to the server to see the log

wind-hx · 2022-04-21T07:01:12Z

is that the only code you're using? can you send a small reproducible code ?

timeout is not a network connection timeout, Some connections will have a timeout, but there is no problem with the network

Error: Cannot send requests while disconnected. You need to call .connect()
    at MTProtoSender.send (/root/telegram-transport/node_modules/telegram/network/MTProtoSender.js:197:19)
    at /root/telegram-transport/node_modules/telegram/client/updates.js:163:47
    at attempts (/root/telegram-transport/node_modules/telegram/client/updates.js:203:26)
    at Object._updateLoop (/root/telegram-transport/node_modules/telegram/client/updates.js:162:13)
Error: TIMEOUT
    at /root/telegram-transport/node_modules/telegram/client/updates.js:218:55
    at attempts (/root/telegram-transport/node_modules/telegram/client/updates.js:203:20)
    at Object._updateLoop (/root/telegram-transport/node_modules/telegram/client/updates.js:162:13)
Error: TIMEOUT
    at /root/telegram-transport/node_modules/telegram/client/updates.js:218:55
    at attempts (/root/telegram-transport/node_modules/telegram/client/updates.js:203:20)
    at Object._updateLoop (/root/telegram-transport/node_modules/telegram/client/updates.js:162:13)
Error: Cannot send requests while disconnected. You need to call .connect()
    at MTProtoSender.send (/root/telegram-transport/node_modules/telegram/network/MTProtoSender.js:197:19)
    at /root/telegram-transport/node_modules/telegram/client/updates.js:163:47
    at attempts (/root/telegram-transport/node_modules/telegram/client/updates.js:203:26)
    at runMicrotasks (<anonymous>)
    at runNextTicks (internal/process/task_queues.js:60:5)
    at listOnTimeout (internal/timers.js:526:9)
    at processTimers (internal/timers.js:500:7)
    at Object._updateLoop (/root/telegram-transport/node_modules/telegram/client/updates.js:162:13)
Error: TIMEOUT
    at /root/telegram-transport/node_modules/telegram/client/updates.js:218:55
    at runMicrotasks (<anonymous>)
    at runNextTicks (internal/process/task_queues.js:60:5)
    at listOnTimeout (internal/timers.js:526:9)
    at processTimers (internal/timers.js:500:7)
    at attempts (/root/telegram-transport/node_modules/telegram/client/updates.js:203:20)
    at Object._updateLoop (/root/telegram-transport/node_modules/telegram/client/updates.js:162:13)
Error: Cannot send requests while disconnected. You need to call .connect()
    at MTProtoSender.send (/root/telegram-transport/node_modules/telegram/network/MTProtoSender.js:197:19)
    at /root/telegram-transport/node_modules/telegram/client/updates.js:163:47
    at attempts (/root/telegram-transport/node_modules/telegram/client/updates.js:203:26)
    at Object._updateLoop (/root/telegram-transport/node_modules/telegram/client/updates.js:162:13)

gramjs/gramjs/client/updates.ts

Line 258 in b6b46c8

sleep(ms).then(() => Promise.reject(new Error("TIMEOUT"))),

painor · 2022-04-21T10:28:46Z

You can find me in https://t.me/gramjschat

MichaelCasaDev · 2022-05-09T07:35:37Z

There are updates on this topic?

painor · 2022-05-09T09:02:53Z

There are updates on this topic?

The latest version should have had some fixes for this.

emiliocr90 · 2023-10-18T08:33:56Z

Hi guys. I'm using version 2.17.4 and still getting timout on error log.

Error: TIMEOUT
at /home/user/node_modules/telegram/client/updates.js:244:85
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at processTimers (node:internal/timers:514:7)
at attempts (/home/user/node_modules/telegram/client/updates.js:228:20)
at _updateLoop (/home/user/node_modules/telegram/client/updates.js:180:17)
Error: TIMEOUT
at /home/user/node_modules/telegram/client/updates.js:244:85
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at processTimers (node:internal/timers:514:7)
at attempts (/home/user/node_modules/telegram/client/updates.js:228:20)
at _updateLoop (/home/user/node_modules/telegram/client/updates.js:180:17)
Error: TIMEOUT
at /home/user/node_modules/telegram/client/updates.js:244:85
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at processTimers (node:internal/timers:514:7)
at attempts (/home/user/node_modules/telegram/client/updates.js:228:20)
at _updateLoop (/home/user/node_modules/telegram/client/updates.js:180:17)
Error: TIMEOUT
at /home/user/node_modules/telegram/client/updates.js:244:85
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at processTimers (node:internal/timers:514:7)
at attempts (/home/user/node_modules/telegram/client/updates.js:228:20)
at _updateLoop (/home/user/node_modules/telegram/client/updates.js:180:17)
Error: TIMEOUT
at /home/user/node_modules/telegram/client/updates.js:244:85
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at processTimers (node:internal/timers:514:7)
at attempts (/home/user/node_modules/telegram/client/updates.js:228:20)
at _updateLoop (/home/user/node_modules/telegram/client/updates.js:180:17)
Error: TIMEOUT
at /home/user/node_modules/telegram/client/updates.js:244:85
at attempts (/home/user/node_modules/telegram/client/updates.js:228:20)
at _updateLoop (/home/user/node_modules/telegram/client/updates.js:180:17)

emiliocr90 · 2023-10-18T08:40:32Z

my code:

async main(): Promise<void>
    {       
    const sessionTxt: string = fs.readFileSync(__dirname + '/data/session.txt', {encoding: 'utf-8'}),
              stringSession: StringSession = new StringSession(sessionTxt),
              client: TelegramClient = new TelegramClient(stringSession, *, '*', {connectionRetries: 10});

        client.setLogLevel(LogLevel.ERROR);
        await client.start(
        {
            phoneNumber: '*', 
            phoneCode: async () => await input.text('Code:'), 
            onError: (err) => console.error(err)
        });
        fs.writeFileSync(__dirname + '/data/session.txt', (<StringSession> client.session).save(), {encoding: 'utf-8', flag: 'w'});

        do
        {
            client.connect();
            await sleep(2000);
            if(!client.connected) fs.writeFileSync(__dirname + '/logs/connect_log', new Date() + ' Not connected' + '<br>\n<br>\n', {encoding: 'utf-8', flag: 'a'});
        }
        while(!client.connected);

        let lastMessages: Api.TypeMessage[], lastMessage: Api.Message;

        lastMessages = (<Api.messages.Messages> await client.invoke(new Api.messages.GetHistory(
        {
            peer: <bigInt.BigInteger> (<unknown> -1001717037581),
            limit: 20
        }))).messages;

        lastMessages.forEach((msg: Api.Message) =>
        {
            if(msg.replyTo === null)
                if(msg.message && msg.message.startsWith('🔥'))
                {
                    if((Date.now() - msg.date*1000) < 120000)
                    {
                        const lines: string[] = msg.message.split('\n\n'),
                              config: any = JSON.parse(fs.readFileSync(__dirname + '/data/config.json', {encoding: 'utf-8'})),
                              excluded: boolean = config.excluded;
                              
                        if(!excluded) this.doSomething();
                        
                        fs.writeFileSync(__dirname + '/logs/telegram_log', new Date() + `\n ${msg.message} \n\n`, {encoding: 'utf-8', flag: 'a'});
                    }                    
                }
        });

        client.disconnect();
    }

this code is executed every minute by a cronjob.

SJPiran · 2023-10-21T17:49:07Z

my code:

async main(): Promise<void>
    {       
    const sessionTxt: string = fs.readFileSync(__dirname + '/data/session.txt', {encoding: 'utf-8'}),
              stringSession: StringSession = new StringSession(sessionTxt),
              client: TelegramClient = new TelegramClient(stringSession, *, '*', {connectionRetries: 10});

        client.setLogLevel(LogLevel.ERROR);
        await client.start(
        {
            phoneNumber: '*', 
            phoneCode: async () => await input.text('Code:'), 
            onError: (err) => console.error(err)
        });
        fs.writeFileSync(__dirname + '/data/session.txt', (<StringSession> client.session).save(), {encoding: 'utf-8', flag: 'w'});

        do
        {
            client.connect();
            await sleep(2000);
            if(!client.connected) fs.writeFileSync(__dirname + '/logs/connect_log', new Date() + ' Not connected' + '<br>\n<br>\n', {encoding: 'utf-8', flag: 'a'});
        }
        while(!client.connected);

        let lastMessages: Api.TypeMessage[], lastMessage: Api.Message;

        lastMessages = (<Api.messages.Messages> await client.invoke(new Api.messages.GetHistory(
        {
            peer: <bigInt.BigInteger> (<unknown> -1001717037581),
            limit: 20
        }))).messages;

        lastMessages.forEach((msg: Api.Message) =>
        {
            if(msg.replyTo === null)
                if(msg.message && msg.message.startsWith('🔥'))
                {
                    if((Date.now() - msg.date*1000) < 120000)
                    {
                        const lines: string[] = msg.message.split('\n\n'),
                              config: any = JSON.parse(fs.readFileSync(__dirname + '/data/config.json', {encoding: 'utf-8'})),
                              excluded: boolean = config.excluded;
                              
                        if(!excluded) this.doSomething();
                        
                        fs.writeFileSync(__dirname + '/logs/telegram_log', new Date() + `\n ${msg.message} \n\n`, {encoding: 'utf-8', flag: 'a'});
                    }                    
                }
        });

        client.disconnect();
    }

this code is executed every minute by a cronjob.

I'd have the same problem, I think this is a Gram js bug, and I hope that will be fixed in the next version

SJPiran · 2023-10-21T19:21:03Z

for this error (Error: TIMEOUT
at /home/user/node_modules/telegram/client/updates.js:244:85)

go to this file (updates.js) line 244 and remove await before the promise. enjoy!

MichaelCasaDev · 2023-10-25T14:51:48Z

go to this file (updates.js) line 244 and remove await before the promise. enjoy!

I don't think is good for production this...

davie-robertson · 2024-01-21T22:45:47Z

I've upgraded to 2.19.10 and I'm now facing this, I don't think I had the issue in 2.17.4

0xluc · 2024-05-07T22:33:40Z

Is there any way to avoid this error being logged?

binamralamsal · 2024-05-28T16:47:10Z

I am also facing same issue on v2.20.15
Edit: Same problem even on v2.21.2

sapn1s · 2024-06-18T10:35:26Z

For anyone having Error: TIMEOUT spam problem:
(For me it occurs because I disconnect client without destroying it, so I can later connect using the same client)

You can disable all logs using client.setLogLevel("none");

And to actually be able to handle the errors instead of only getting them spammed, define your logger function and assign it to the client:

// Define the error handler function:
async function errorHandler(error) {
    if (error.message && error.message == 'TIMEOUT') {
        //Do nothing, as this error does not make sense to appear while keeping the client disconnected
    } else {
        console.error(`Error occurred for API ID ${this.apiId}:`, error);
        // Handle other types of errors
    }}
    
 //Assign this handler to client: 
client._errorHandler = errorHandler

You can not keep info/warn logs with something like client.setLogLevel("info"); because logger is defined as levels: [ 'error', 'warn', 'info', 'debug' ] and whatever your choice is, it will log everything to the left in the array for the level of your choice.

So to keep info/warning logs, you need to re-define the log levels array:

client._log.levels = ['warn', 'info', 'error','debug' ];
client.setLogLevel("info");

Thus, the result is that you still get all the other logs while errors can actually be handled.

wind-hx changed the title ~~can't reconnect Error: TIMEOUT I'm using version 2.6.11~~ can't reconnect Error: TIMEOUT I'm using version 2.6.13 Apr 20, 2022

wind-hx mentioned this issue Apr 20, 2022

Error: Cannot send requests while disconnected. You need to call .connect() #303

Closed

wind-hx changed the title ~~can't reconnect Error: TIMEOUT I'm using version 2.6.13~~ TIMEOUT I'm using version 2.6.13 Apr 21, 2022

fastndead mentioned this issue Oct 18, 2024

AUTH_KEY_DUPLICATED after running for a while #733

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

TIMEOUT I'm using version 2.6.13 #302

TIMEOUT I'm using version 2.6.13 #302

wind-hx commented Apr 20, 2022 •

edited

Loading

wind-hx commented Apr 20, 2022

painor commented Apr 20, 2022

wind-hx commented Apr 21, 2022

wind-hx commented Apr 21, 2022

wind-hx commented Apr 21, 2022 •

edited

Loading

painor commented Apr 21, 2022

MichaelCasaDev commented May 9, 2022

painor commented May 9, 2022

emiliocr90 commented Oct 18, 2023 •

edited

Loading

emiliocr90 commented Oct 18, 2023 •

edited

Loading

SJPiran commented Oct 21, 2023

SJPiran commented Oct 21, 2023

MichaelCasaDev commented Oct 25, 2023

davie-robertson commented Jan 21, 2024

0xluc commented May 7, 2024

binamralamsal commented May 28, 2024 •

edited

Loading

sapn1s commented Jun 18, 2024 •

edited

Loading

TIMEOUT I'm using version 2.6.13 #302

TIMEOUT I'm using version 2.6.13 #302

Comments

wind-hx commented Apr 20, 2022 • edited Loading

wind-hx commented Apr 20, 2022

painor commented Apr 20, 2022

wind-hx commented Apr 21, 2022

wind-hx commented Apr 21, 2022

wind-hx commented Apr 21, 2022 • edited Loading

painor commented Apr 21, 2022

MichaelCasaDev commented May 9, 2022

painor commented May 9, 2022

emiliocr90 commented Oct 18, 2023 • edited Loading

emiliocr90 commented Oct 18, 2023 • edited Loading

SJPiran commented Oct 21, 2023

SJPiran commented Oct 21, 2023

MichaelCasaDev commented Oct 25, 2023

davie-robertson commented Jan 21, 2024

0xluc commented May 7, 2024

binamralamsal commented May 28, 2024 • edited Loading

sapn1s commented Jun 18, 2024 • edited Loading

wind-hx commented Apr 20, 2022 •

edited

Loading

wind-hx commented Apr 21, 2022 •

edited

Loading

emiliocr90 commented Oct 18, 2023 •

edited

Loading

emiliocr90 commented Oct 18, 2023 •

edited

Loading

binamralamsal commented May 28, 2024 •

edited

Loading

sapn1s commented Jun 18, 2024 •

edited

Loading