-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not deserialize persisted model #443
Comments
I see similar messages (at warning, error and fatal level) in my log (using NC 21.0.1 with suspicious_login 4.0.0):
and
and
I redacted [username] and [ipv6 address]. At first sight there seems to be an issue with how ipv6 addresses are handled. |
did this possibly happen shortly after an upgrade? do you have the mail app enabled as well? |
@ChristophWurst Yes happened shortly after the upgrade (both NC and suspicious_login), a couple of times. After that I didn't see it happen back again. No, mail app isn't enabled. |
I see. Then this is actually expected. With v4 we had to switch out the old ML lib. The new lib can't load the serialized object of the old lib. Once the app did a daily retraining of the model the error should go away. |
OK; that's definitely consistent with what I observed. But perhaps the case should be provided for somewhere in the code such that no errors result? |
Yeah, ideally. Right now the best you can do as admin is running a training job from the CLI manually right after the upgrade. I should have included that in the changelog. |
OK, I think we can close this one. There's more obscure issues that need attention. |
Hey, the error still occures. Can i execute a cli command to fix it? |
Yeah we may have concluded to soon. The errors are coming back, even when more than 24h have passed since upgrading to V4. |
Could you please share the contents of such a model file? You'll find that in |
@ChristophWurst Attached. |
I'm seeing Sometimes I see |
Hello, similar here, but with mail-app enabled.
|
Could you elaborate on this? I checked my personal instance, the last model from |
Hello Christoph, indeed - I just checked again: the latest file in Happy to dig further in case that helps - just let me know. LG - tullsta |
Whoops. Do you have a job for |
Hi Christoph, maybe stupid question: how do I report the In case it gives additional info: LG - tullsta PS: Running official NC docker image |
|
Hi - hope I got things right: MariaDB [(none)]> use nextcloud |
nope, you forgot to double-escape the string |
|
Hi Christoph, was now a little puzzled, but I did double-escape like: it's just that Github replaces double-escapes with single ones when pasting as normal text.
LG - tullsta |
Try disabling and re-enabling the app. I hope that brings the job back. I don't know why it's missing for you. |
Hey Christoph, re-installed app and restarted container now, but could not see any change yet. LG - tullsta |
Hello - just wanted to ask whether there is a way to re-enable the background job. Thanks - tullsta |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I do have these
I have no Whether I disable the app or reactivate it, these jobs stay.... not sure if normal or not. Meanwhile, I manually launched |
I also can see those errors for some of the models, they seem to be all of the removed Phpml type:
The actual file is also untouched since two years: |
All right, seems to be mostly because the model for ipv6 was never generated on my instance with the Rubix\ML classes, after applying #644 and running |
I have a lot of following errors on NC protocol:
"Could not deserialize persisted model 254: Missing class definition for unserialized object."
Here are the raw data:
{"reqId":"tDWLs8oLa6wApE1uFe9r","level":4,"time":"2021-04-12T10:19:43+00:00","remoteAddr":"192.168.1.101","user":"sync","app":"suspicious_login","method":"REPORT","url":"/remote.php/dav/addressbooks/users/sync/gemeinsam/","message":"Could not deserialize persisted model 254: Missing class definition for unserialized object.","userAgent":"macOS/11.2.3 (20D91) AddressBookCore/2452.4","version":"21.0.1.1","id":"60741ec2b4442"}
Steps to reproduce
Expected behaviour
Contact sync is ok. I have very much denied http request regarding to contact/calendar sync. I dont know, if this have something to do with each other.
Actual behaviour
This error in nc protocol
Server configuration
**Operating system: linuxserver/nextcloud docker image
**Web server: nginx (linuxserver/nextcloud docker image)
**Database: MariaDB (linuxserver/nextcloud docker image)
**PHP version: 7.4.15
**Nextcloud version: 21.0.1
**Updated from an older Nextcloud/ownCloud or fresh install: Updated from 20.xx
**Where did you install Nextcloud from: docker image
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
**Are you using external storage, if yes which one: no
**Are you using encryption: no
**Are you using an external user-backend, if yes which one: no
Client configuration
**Browser: Brave
**Operating system: MacOS
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
The text was updated successfully, but these errors were encountered: