Error loading Pages (Recording&Supervision)

Mostafaie

Hi,
Today, I got the "Something Went wrong here 500" internal error without any reason
I upgraded the oml to the lates version 1.18.0, but the error is on.
This error is opt/omnileads/log/django.log repeated
2021-09-21 22:40:03,784 [ ERROR] reportes_app.management.commands.actualizar_reportes_llamadas_salientes - Fallo del comando: module 'datetime' has no attribute 'fromtimestamp'
I`ve got no clue what to do
please help, this is urgent

Mostafaie

By the way, I could upgrade without any warning or error and because github and some other sites are banned to access in my country I have to route internet access of the server through a vpn .
without using vpn I am not able to login ever, Even local

Mostafaie

django.log http://linkode.org/#2g0qS9COWRrIRHSxjZVp2
oml_uwsgi.log http://linkode.org/#Amk4ef5LfbF13yWIwO16O

Mostafaie

OMniLeads version 1.18.0
Environment: OnPremise & WAN access

Mostafaie

By doing installation more and more ( ./deploy.sh -u), part of problems solved, but supervision monotoring agent still not work and getting "internal error 500"
Everytime I do upgrade I will get successful message

FernandoMontiel

Hi @Mostafaie.

On first Linkode message you uploaded, I see that the application couldn't connect to Asterisk via AMI:

2021-09-21 22:56:04,647 [ ERROR] ominicontacto_app.services.asterisk.asterisk_ami - Error logging in to the manager: Authentication failed

Did you change credentials on inventory file, before running "./deploy.sh -u"? Did you solve it rolling that parameters back to the previous values?

Regarding supervision, it seems there's a problem when trying to get data from Redis. Can you check if you did the same thing than previous point on AMI? Maybe you changed redis parameters on inventory file. Can you check Redis status? On console, execute "redis-cli" as root, and check keys executing "KEYS *":

[root@oml ~]# redis-cli 
127.0.0.1:6379> KEYS *

Send us the results on Linkode again.

Let me know.

Best regards.

Mostafaie

Hi,
Result from redis-cli http://linkode.org/#5Wq5qY3hBzYzAYf2I5Rcg2
django.log http://linkode.org/#j3gRGxmntbdfJHpKo5iXN2
I think I did that changes before running "./deploy.sh -u". Now what should I do?
but after repeating update procedures, my first problem solved."Login agent error" But on admin, they couldn't see supervision pages.
oml_uwsgi.log when I access supervision/Agent page http://linkode.org/#IXUpo6FinpaM6cvzDP3Nd4
Can you tell me, the agent and admin web panel need to see what's sites to open correctly?
I mean from the server, whenever I disable oml internet access the admin page never show up and I get error 500

FernandoMontiel

Hi @Mostafaie.

Regarding Supervision error, I see that a redisgears command (RG.PYEXECUTE) can't be executed. So, you need to check if RedisGears is loaded on Redis. Here, some things to check:

You should see this line on /etc/redis.conf:

[root@CentOS7-Fresh ~]# cat /etc/redis.conf | grep redisgears
loadmodule /usr/lib64/redis/modules/redisgears-1.0.3.so

You should see that file in place:

[root@CentOS7-Fresh ~]# ls -l /usr/lib64/redis/modules/redisgears-1.0.3.so
-rwxr-xr-x. 1 root root 4535648 Apr 28 12:29 /usr/lib64/redis/modules/redisgears-1.0.3.so

You should check if RedisGears is running:

[root@CentOS7-Fresh ~]# redis-cli RG.PYEXECUTE "GearsBuilder().run()"

You should check any error on /var/log/redis/redis.log. Please, send us also this log. You can add verbosity, modifying the file /etc/redis.conf on line regarding "loglevel", changing from notice to debug, and restarting redis (service redis restart). After that, you can roll back to notice.

Mostafaie

Hi,
First, the result of your commands http://linkode.org/#feFPHMdJHX2sqW6glpviN4
2nd, rdis.log http://linkode.org/#jEu8OdN9q6701UtJ572ox2

FernandoMontiel

Hi @Mostafaie.

Can you send us, the complete Redis configuration file via Linkode? (/etc/redis.conf)

Mostafaie

Hi,
Here you are http://linkode.org/#M5NGNWhXzddGtbk7L3Ncl5
I deleted some comments because of LINKCODE limitation

FernandoMontiel

Hi,.

I think it's not complete, as there is no line for loading redisgears.

Can you send it to info@omnileads.net?

Let me know once you did it.

Mostafaie

Hi, it mailed right now

FernandoMontiel

Hi @Mostafaie.

I don't see the line for loading RedisGears module, on the file you sent me:

[root@CentOS7-Fresh etc]# cat /etc/redis.conf|grep redisgears
[root@CentOS7-Fresh etc]#

That command, returns nothing in your file. As I told you before, you should see this:

[root@CentOS7-Fresh ~]# cat /etc/redis.conf | grep redisgears
loadmodule /usr/lib64/redis/modules/redisgears-1.0.3.so

Also, I don't see the line for binding the service to localhost:

bind 127.0.0.1

Did you make changes on this file?

Please, have a look at the file /etc/redis.conf, and make sure the following 2 lines are on that file:

loadmodule /usr/lib64/redis/modules/redisgears-1.0.3.so
bind 127.0.0.1

If they are not on the file, add them at the bottom.

After that, perform a restart of Redis with the follwing command:

service redis restart

Send us the results on Linkode of the previous command.

Best regards.

Mostafaie

OMG,
That was totally helpful.
I just add
loadmodule /usr/lib64/redis/modules/redisgears-1.0.3.so
bind 127.0.0.1
at the end of redis.conf then run service redis restart command
Thank you alot

FernandoMontiel

Great! 🙂