writing my own telegram bot
bot working good but after 2-3 days working i saw that
python3[87844]: INFO:pyrogram.connection.connection:Disconnected
python3[87844]: INFO:pyrogram.session.session:Session stopped
python3[87844]: INFO:pyrogram.connection.connection:Connecting...
python3[87844]: INFO:pyrogram.connection.connection:Connected! Production DC2 - IPv4 - TCPAbridgedO
python3[87844]: INFO:pyrogram.session.session:NetworkTask started
python3[87844]: INFO:pyrogram.session.session:Session initialized: Layer 145
python3[87844]: INFO:pyrogram.session.session:Device: CPython 3.10.6 - Pyrogram 2.0.51
python3[87844]: INFO:pyrogram.session.session:System: Linux 5.15.0-52-generic (EN)
python3[87844]: INFO:pyrogram.session.session:Session started
python3[87844]: INFO:pyrogram.session.session:PingTask started
and my bot doesn't work and now i don't know what to do with that only to restart, but this not good solution, please help)
Related
I was implementing the fabric v2.2 Hyperledger fabric sample > test-network, all the binaries and module versions are updated and satisfied but while creating channel getting this error as highlighted as shown click to see error
I have not used v2.2 before but I have successfully used v1.4 and 2.1 before and what can tell you is that "join transactions" are submitted to the orderer in the network.
The orderer has a port number of 7050. So you can try the code below to see if your orderer is listening on port 7053 or 7050.
telnet localhost 7053
telnet localhost 7050
Before trying the codes, make sure you start your network.
A couple of days ago i tried this tool for a little project and it goes without errors for now, but the service looks inactive (exited) so this is what im doing actually.
Im using Centos 7 virtual machine on VMware and Zimbra open source 8.7.10. I read tutorials about setup zimbra, I make a dns name on the same virtual machine but Im not sure if this works good or I have to install another Centos for doing DNS server work.
I tested the DNS I made with Windows 8.1 (installed on my dektop machine) with nslookup adding ip on dns net properties and it got response.
I cant enter on Zimbra web console, maybe Im missing something.
[root#mail ~]# systemctl status zimbra
● zimbra.service - LSB: Zimbra mail service
Loaded: loaded (/etc/rc.d/init.d/zimbra; bad; vendor preset: disabled)
Active: active (exited) since vie 2017-06-30 11:43:34 -04; 19min ago
Docs: man:systemd-sysv-generator(8)
Process: 834 ExecStart=/etc/rc.d/init.d/zimbra start (code=exited,
status=0/SUCCESS)
jun 30 11:42:03 mail zimbra[834]: Starting opendkim...Done.
jun 30 11:42:03 mail zimbra[834]: Starting snmp...Done.
jun 30 11:42:05 mail zimbra[834]: Starting spell...Done.
jun 30 11:42:10 mail zimbra[834]: Starting mta...Done.
jun 30 11:42:12 mail zimbra[834]: Starting stats...Done.
jun 30 11:42:23 mail zimbra[834]: Starting service webapp...Done.
jun 30 11:42:29 mail zimbra[834]: Starting zimbra webapp...Done.
jun 30 11:42:30 mail zimbra[834]: Starting zimbraAdmin webapp...Done.
jun 30 11:42:30 mail zimbra[834]: Starting zimlet webapp...Done.
jun 30 11:43:35 mail systemd[1]: Started LSB: Zimbra mail service.
I hope you can help me, thank you in advance.
now i can use zimbra. The error were 2, the first one was allowing port 7071 on Server side, the other was the DNS config, this last one is just pointing to Zimbra IP in DNS field. Even i can send mails to gmail what i think it was impossible, jaja.
Anyway thank you, but if someone have a good practices for zimbra Im all ears. I mean certificates for tls/ssl for clients believe its safe.
Cheers!
after upgrading a node in cassandra, these error in log occured:
I want to investigate but dont have a direction, any clue will help
thanks
2016/09/19 06:24:49 [INFO] core: post-unseal setup starting
2016/09/19 06:24:49 [INFO] core: mounted backend of type generic at secret/
2016/09/19 06:24:49 [INFO] core: mounted backend of type cubbyhole at cubbyhole/
2016/09/19 06:24:49 [INFO] core: mounted backend of type system at sys/
2016/09/19 06:24:49 [INFO] core: mounted backend of type cassandra at cassandra/
2016/09/19 06:24:49 [INFO] rollback: starting rollback manager
2016/09/19 06:24:50 [INFO] expire: restored 2 leases
2016/09/19 06:24:50 [INFO] core: post-unseal setup complete
2016/09/19 06:24:55 gocql: unable to dial control conn node-0.cassandra-app.mesos:9042: dial tcp 10.0.2.42:9042: getsockopt: connection refused
2016/09/19 06:25:12 error: failed to connect to 10.0.2.42:9042 due to error: gocql: no response to connection startup within timeout
Cassandra cluster is not cross-version compatible, you can not upgrade a node only, you have to upgrade the cluster. This is a common mistake people tend to do, please see this video here it mentiones this problem, also it is very very useful with lots of good info.
I have setup a node.js application and it's running on port 4999, but when I browse to the url www.website.com:4999 I get a This site can’t be reached error in Chrome and Secure Connection Failed in Firefox
The is the code in SSH used to start the node app
[~/public_html/customer_portal]# gulp serv:prod
[13:48:50] Using gulpfile ~/public_html/customer_portal/gulpfile.js
[13:48:50] Starting 'ConcatScripts'...
[13:48:50] Starting 'ConcatCss'...
[13:48:50] Starting 'CopyAssets'...
[13:48:50] Finished 'ConcatCss' after 553 ms
[13:48:50] Starting 'UglyCss'...
[13:48:50] Finished 'CopyAssets' after 855 ms
[13:48:50] Finished 'UglyCss' after 322 ms
[13:48:50] Finished 'ConcatScripts' after 925 ms
[13:48:50] Starting 'UglyScripts'...
[13:49:08] Finished 'UglyScripts' after 18 s
[13:49:08] Starting 'Inject:PROD'...
[13:49:08] gulp-inject 1 files into index.build.ejs.
[13:49:08] gulp-inject 1 files into index.build.ejs.
[13:49:08] Finished 'Inject:PROD' after 218 ms
[13:49:08] Starting 'build:prod'...
[13:49:08] Finished 'build:prod' after 61 μs
[13:49:08] Starting 'serv:prod'...
[13:49:08] Finished 'serv:prod' after 48 ms
livereload[tiny-lr] listening on 35729 ...
Mon, 25 Jul 2016 03:49:09 GMT express-session deprecated undefined saveUninitialized option; provide saveUninitialized option at app.js:58:13
XXX service has been started at port: 4999 !!!
Just compiling the solution we derived from the comment in OP's post.
So OP had tested his nodeJS application locally and now he is wanting to expose it to the world wide web. While OP did not post content of his gulpFile but I am guessing that he is trying to use a development server spin up by gulp to serve his web page. Not impossible, however certainly not recommended.
A better replacement would be to use a real web server like nginx.
See:
https://nginx.org/en/docs/beginners_guide.html
Back to the original problem. The real reason why OP is getting hit by the error This site can’t be reached was probably because his server did not have the required port forwarded, in this case port 4999. To workaround this temporarily would be to update the Gulp file to host the application on port 80 instead.
However I am still dubious about the error message because I would have thought OP should see something like connection refused. Anyway, this is not important.
To sum up, OP should consider fixing his problem by;
install a real web server on his machine
place the application onto the installed web server
Ubuntu 10.04 system. new Plone install, went fine and created some content, everything seemed fine. New kernel update and a reboot later, Plone is running but will not present any pages to a browser. In fact, a browser attempt just times out. I can telnet to the port 8080 on the system and send an HTTP get by hand and nothing comes back. The log file for client1 in a zeo install keeps repeating:
2011-08-10T16:59:57 INFO ZServer HTTP server started at Wed Aug 10 16:59:57 2011
Hostname: 0.0.0.0
Port: 8080
------
2011-08-10T16:59:57 INFO Zope Set effective user to "plone"
------
2011-08-10T17:00:02 INFO ZEO.ClientStorage zeostorage ClientStorage (pid=24596) created RW/normal for storage: '1'
------
2011-08-10T17:00:02 INFO ZEO.cache created temporary cache file '<fdopen>'
------
2011-08-10T17:00:02 INFO ZEO.ClientStorage zeostorage Testing connection <ManagedClientConnection ('127.0.0.1', 8100)>
------
2011-08-10T17:00:02 INFO ZEO.zrpc.Connection(C) (127.0.0.1:8100) received handshake 'Z3101'
------
2011-08-10T17:00:02 INFO ZEO.ClientStorage zeostorage Server authentication protocol None
------
2011-08-10T17:00:02 INFO ZEO.ClientStorage zeostorage Connected to storage: ('dns', 8100)
------
2011-08-10T17:00:02 INFO ZEO.ClientStorage zeostorage No verification necessary -- empty cache
------
2011-08-10T17:00:22 INFO ZServer HTTP server started at Wed Aug 10 17:00:22 2011
Hostname: 0.0.0.0
Port: 8080
I haven't been able to find any other info on what is causing this, nor can I find any documentation on debugging a Plone install.
Thanks for any help you can provide.
Forgive the aborted answer, misread the log snippet. The repeated log entries you're seeing are what you'd expect to see from repeated restarts. Are you repeatedly restarting the instance? If not, then in it seems your instance is restarting on it's own. Shut down the instance and start it using "bin/instance fg" and see if that gives you more information.