Cant sync mail

[jvonau]

Installed via curl install.py
fished this out of /lokole/logs/lokole_celery_worker.stderr.log

[2021-05-13 15:35:43,700: ERROR/ForkPoolWorker-1] Task opwen_email_client.webapp.tasks.sync[8af92df3-5f9b-4dda-a917-8f6d1ff96452] raised unexpected: TypeError('gethostbyname() argument 1 must be str, bytes or bytearray, not None')
Traceback (most recent call last):
File "/lokole/venv/lib/python3.7/site-packages/celery/app/trace.py", line 412, in trace_task
R = retval = fun(*args, **kwargs)
File "/lokole/venv/lib/python3.7/site-packages/celery/app/trace.py", line 704, in protected_call
return self.run(*args, **kwargs)
File "/lokole/venv/lib/python3.7/site-packages/opwen_email_client/webapp/tasks.py", line 41, in sync
if check_connection(AppConfig.STORAGE_ACCOUNT_HOST, 80):
File "/lokole/venv/lib/python3.7/site-packages/opwen_email_client/util/network.py", line 7, in check_connection
host = gethostbyname(hostname)
TypeError: gethostbyname() argument 1 must be str, bytes or bytearray, not None

pi@raspberrypi:~ $ cat /lokole/state/settings.env

OPWEN_APP_ROOT=
OPWEN_STATE_DIRECTORY=/lokole/state
OPWEN_SESSION_KEY=edit
OPWEN_MAX_UPLOAD_SIZE_MB=10
OPWEN_SIM_TYPE=Ethernet
OPWEN_EMAIL_SERVER_HOSTNAME=mailserver.lokole.ca
OPWEN_CLIENT_NAME=jv-rpi-stock
OPWEN_ROOT_DOMAIN=lokole.ca
OPWEN_RESTART_PATH=/lokole/state/lokole_restarter/lokole_gunicorn=HUP,/lokole/state/lokole_restarter/lokole_celery_worker=,/lokole/state/lokole_restarter/lokole_celery_beat=
OPWEN_SYNC_SCHEDULE=1,16,31,46
OPWEN_CLIENT_ID=edit
OPWEN_REMOTE_ACCOUNT_NAME=edit
OPWEN_REMOTE_ACCOUNT_KEY=edit
OPWEN_REMOTE_RESOURCE_CONTAINER=compressedpackages

Only the server has this variable passed to the running processes. Think this would need to be embedded in the registration reply info.

[holta]

@nzola is stuck likewise? In any case, he just wrote:

I cannot send or receive emails. All outgoing email from Lokole clients are stack in the outbox and all the inbound emails coming from the internet are stack in the Lokole srver, I can see the number of emaills in the server status. This situation is just with any clients I setup with ver 0.6.14. But I still have the client I created with 0.6.10. it is sill exchanging emails without any problems. I have not upgraded it yet.

[jvonau]

@nzola Please email privately me the contents of /lokole/state/settings.env from the 0.6.10 machine please.

[nzola]

@jvonau I rushed to catch the bus. I will send it late at midnight when I am home

[adamsclafani]

The piece of code where the error was being thrown was a new(well not so new anymore) piece that was added as part of the IIAB integration funny enough, discussion here. check_connection() basically checks for an existing connection before attempting to dial up via a USB modem.

In short, as @jvonau pointed out, the OPWEN_REMOTE_ACCOUNT_HOST variable is not set. This should also probably be returned in the register UI. That being said, @nzola is using the install script so it is definitely odd that this variable would not be set.

[adamsclafani]

Looking at the install script, it does not even mention or set the OPWEN_REMOTE_ACCOUNT_HOST variable. Maybe this should be 'mailserver.lokole.ca'. Maybe I should just change it it 'OPWEN_EMAIL_SERVER_HOSTNAME'?

[nzola]

Noticed 3 vwdial files and a directory are missing in the state directory of the new client install compared to ver 0.6.10 install

Folder for victest1 client ver 0.6.10:

pi@raspberrypi:/lokole/state $ ls
celery.cron.db lokole_celery_beat.pid settings.env wvdial.log
celery.sqlite3 lokole_gunicorn.sock users.sqlite3 wvdial.log.bak.gz
emails.sqlite3 lokole_restarter wvdial
pi@raspberrypi:/lokole/state $

Folder for victest9 client ver 0.6.14:

pi@raspberrypi:/lokole/state $ ls
celery.cron.db emails.sqlite3 lokole_gunicorn.sock settings.env
celery.sqlite3 lokole_celery_beat.pid lokole_restarter users.sqlite3
pi@raspberrypi:/lokole/state $

[nzola]

I don't know why those crossing lines?

[holta]

Thanks @nzola for having shared:

pi@raspberrypi:~ $ cd lokole
pi@raspberrypi:~/lokole $ ls
logs  state  venv
pi@raspberrypi:~/lokole $ cd state
pi@raspberrypi:~/lokole/state $ ls
celery.cron.db  emails.sqlite3          lokole_gunicorn.sock  settings.env
celery.sqlite3  lokole_celery_beat.pid  lokole_restarter      users.sqlite3
pi@raspberrypi:~/lokole/state $

@jvonau requests you post the contents of this file:

/home/pi/lokole/state/settings.env

[holta]

I don't know why those crossing lines?

@nzola use triple backticks ``` before and after any code block — to make it easier to read:

https://docs.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks

[nzola]

Folder for victest1 client ver 0.6.10:

pi@raspberrypi:/lokole/state $ ls
celery.cron.db lokole_celery_beat.pid settings.env wvdial.log
celery.sqlite3 lokole_gunicorn.sock users.sqlite3 wvdial.log.bak.gz
emails.sqlite3 lokole_restarter wvdial
pi@raspberrypi:/lokole/state $

Folder for victest9 client ver 0.6.14:

pi@raspberrypi:/lokole/state $ ls
celery.cron.db emails.sqlite3 lokole_gunicorn.sock settings.env
celery.sqlite3 lokole_celery_beat.pid lokole_restarter users.sqlite3
pi@raspberrypi:/lokole/state $

[jvonau]

Lets get some timestamps
ls -l /lokole/state/
ls -l /home/pi/lokole/state/
On 0.6.10 does /home/pi/lokole/state/settings.env exist? if so email me the contents as there may be sensitive info that should not be public.

[jvonau]

Replaced the contents of /lokole/venv/lib/python3.7/site-packages/opwen_email_client/util/network.py on jv-rpi-stock with this complete hack

def check_connection(hostname, port):
    print (hostname)
    SOMEHOST= 'mx.sendgrid.net'
    try:
        os.system("ping -c 5 " + SOMEHOST.strip(";")) is 0
        return True
    except OSError:
        pass
    except:
        return False

that would be network.py here, that is enough for check_connection to work and email starts to flow but needs polishing.

@nzola what is a valid address on vic1test that you know works?

[holta]

@nzola:

✅ Triple backticks: ```
❎ Triple-quotes: '''

...before and after any code block.

Make sure triple-backticks are on their own separate line:
https://docs.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks