Replies: 2 comments 1 reply
-
|
I don't know what this "no space" message relates to, a screenshot or screen recording or even a transcript of the complete error message would have been super helpful here. I don't think the mam database is of any issue here, Monal does not try to download everything in the archive, only the messages received or sent since it was last connected to the server. Regarding happy eyeballs: sure, just implement it and create a PR, I will be happy to merge that :) |
Beta Was this translation helpful? Give feedback.
-
|
The app became non-functional with the no space message. I should have photographed it, but was trying to get the person back functional quickly. It was displayed in a colored background across the very top of the screen. I have been grepping the sources and haven't figured out where that happens yet. I understand now why you find my reporting perplexing... Ack about MAM database. As for happy eyeballs, agreed that would be nice, but the norm before happy eyeballs was "resolve the list of addresses with v6 sorted before v4, and try them one at a time until one succeeds or you run out". It really seems like if there is one v6 and one v4, and the v6 fails, then Monal doesn't end up connecting to v4 and working well. It was staying in with the spinning connecting icon for many minutes. But, the app used to connect before I did remove/reinstall. A suggested repro is "register new account where there is no SRV and the domain part of the JID has an A and AAAA records, where connecting to 5222 at the A record works, and connecting to the AAAA record address gets a TCP Reset. |
Beta Was this translation helpful? Give feedback.
-
|
You could send us a logfile showcasing this "new install, then trying to connect" issue you describe when the server does not have a properly working ipv6. See here on how to extract the logfile: https://github.com/monal-im/Monal/wiki/Introduction-to-Monal-Logging Send the file via mail to [email protected] |
Beta Was this translation helpful? Give feedback.
-
I'm healping someone with jabber and they are using Monal on an iPhone, The phone is newish and running up-to-date iOS and Monalf from the iOS app store. The jabber server is ejabberd, a bit old, but working well with other clients. The person had mulitple issues (some only surfaceed while chasing others). I'm asking if these are known before making issues.
Monal reports no space available, but the phone is 128 GB and has 74 GB free. There is 6XX MB of data used in the app per ios storage.
The popup about the storage is on the top of the screen and can't be dismissed, and obscures the other UI elements so you can't get into settings, or rather I did eventually but I had to really be sneaky; normies would not cope.
Not a Monal bug, but I think the servers MAM database was way too big and I pruned and then I nuked it. I now think the nuking was guessing about point 4 wrong, and wasn't necessary; just pruning to 180 days probably was enough.
4 I removed the app and reinstalled and reconfigured the account, sort of like rebooting. That was fine, but Monal would not connect to the server. The server has an A and an AAAA record but ejabberd is only listening on v4 so the v6 SYN gets a R. It seems Monal does not then just try v4. I was able to work around this changing the DNS. Yes, the server is a little buggy but Monal should be doing happy eyeballs, or at least just go down the list of addresses and try them all until one works. This could have been a firewall bug instead of a server dns/config bug, but in this case it wasn't.
I don't mean to sound super gripy; this has been great to have, including iOS push via the gateway, and until today has been working unremarkably (to deliver notifications from HA over xmpp, basically) very well, and the above are pretty minor.
Beta Was this translation helpful? Give feedback.
All reactions