Cellse Home won't run after upgrade to v4

Running on W10, latest MySQL

I configured v3 and it was working fine. The admin console said v4 was available, so I installed it. Since there is no restart in the console, I shut down my browser and killed cmd.exe. I ran the new cells: cells.exe start, and it gives me this:

2022-11-13T17:16:13.185-0600    ←[34mINFO←[0m   ←[32mpydio.rest.activity←[0m    starting        {"service": "pydio.rest.activity", "hook router to": "/a/activity"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x321b9d7]

goroutine 922 [running]:
github.com/pydio/cells/v4/common/utils/fork.(*Process).GetPID(...)
        /source/common/utils/fork/process.go:84
github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe.func1.1()
        /source/common/server/fork/fork.go:96 +0xbd7
github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe.func1()
        /source/common/server/fork/fork.go:156 +0xa2
created by github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe
        /source/common/server/fork/fork.go:84 +0x3bd

and it drops out.

I tried v3 again so I could get to the console and selected v4.0 (instead of latest), and got the same problem.

How do I get v4 to run?

Hello,

I have retested with Win 10 (but with MariaDB), installed in 3.0.9 and upgraded to 4.0.4 and it works fine.

Problem is that when you restart the service at least once with the new binary (e.g. v4.0.4), some migrations on data are performed under the hood and we do not support downgrade migration.

So if you have done v3.x → v4.0.4 → v3.x → v4.0.1 , it is no surprise if your instance is in a broken state.

If you can start again from scratch with your backup and perform only the first migration v3 to v4, and possibly give more logs if you see an error. We then might be able to help.

I saw this error upon the first upgrade, v3 → 4.latest.

I got that, but the first few lines of log you gave are not enough to diagnose the issue.
(the first error and the panic are also most probably unrelated)

The rest of my message was more to warn you that once you moved your data to v4, you cannot simply downgrade the binary…

I started with a new v3.0.09 install, upgraded to v4.0.1. The app still won’t start. Here is the shell output:

Microsoft Windows [Version 10.0.19044.2251]
(c) Microsoft Corporation. All rights reserved.

C:\Users\jojo\Desktop\pydio-cells-3.0.9-windows-amd64>cells4.1.exe start
[INFO] Upgrading Legacy Keyring Format
Binary:
  Package:      Pydio Cells Home Edition
  Version:      4.0.1
  BuildTime:    17 Oct 22 16:18 +0000
  Git Commit:   faa7b809bcaecb43c10714dba1e76562b89c2655
  Go Version:   go1.19.2
  OS/arch:      windows/amd64

Drivers:
  Registry:     mem:///registry
  Broker:       mem:///broker
  Config:       file://C:/Users/jojo/AppData/Roaming/Pydio/cells/pydio.json
  Vault:        file://C:/Users/jojo/AppData/Roaming/Pydio/cells/pydio-vault.json
  Keyring:      file://C:/Users/jojo/AppData/Roaming/Pydio/cells/cells-vault-key
  Certificates: file://C:/Users/jojo/AppData/Roaming/Pydio/cells/certs
  Cache:        bigcache:///cache
  ShortCache:   pm:///shortcache

Networking:
  Hostname:     Win10VM
  Advertise:    127.0.0.1

Monitoring:
  Metrics:      false
  Profiles:     false

Build Settings:
  -compiler:    gc
  -ldflags:      -X github.com/pydio/cells/v4/common.version=4.0.1 -X github.com/pydio/cells/v4/common.BuildStamp=2022-10-17T16:18:23 -X github.com/pydio/cells/v4/common.BuildRevision=faa7b809bcaecb43c10714dba1e76562b89c2655
  CGO_ENABLED:  1
  CGO_CFLAGS:   -D_WIN32_WINNT=0x0400
  CGO_CXXFLAGS: -D_WIN32_WINNT=0x0400
  GOARCH:       amd64
  GOOS: windows
  GOAMD64:      v1

2022-11-16T20:22:02.148-0600    ←[34mINFO←[0m   ←[35mpydio.grpc.registry←[0m    ready
2022-11-16T20:22:02.148-0600    ←[34mINFO←[0m   ←[35mpydio.grpc.broker←[0m      ready
2022-11-16T20:22:02.160-0600    ←[34mINFO←[0m   ←[35mpydio.grpc.config←[0m      ready
2022-11-16T20:22:02.166-0600    ←[34mINFO←[0m   ←[35mpydio.grpc.log←[0m ready
2022-11-16T20:22:02.166-0600    ←[34mINFO←[0m   ←[36mpydio.server.manager←[0m   Discovery services started, carry on to other services
2022-11-16T20:22:02.210-0600    ←[34mINFO←[0m   ←[36mpydio.gateway.grpc←[0m     Configuring self-signed configuration for gRPC gateway to allow full TLS chain.
2022-11-16T20:22:02.233-0600    ←[34mINFO←[0m   ←[32mpydio.rest.user←[0m        starting        {"service": "pydio.rest.user", "hook router to": "/a/user"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x390b9d7]

goroutine 919 [running]:
github.com/pydio/cells/v4/common/utils/fork.(*Process).GetPID(...)
        /source/common/utils/fork/process.go:84
github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe.func1.1()
        /source/common/server/fork/fork.go:96 +0xbd7
github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe.func1()
        /source/common/server/fork/fork.go:156 +0xa2
created by github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe
        /source/common/server/fork/fork.go:84 +0x3bd

caddy_errors.log is empty
The other logs don’t show anything pertinent; of course, it doesn’t log anything now since it won’t run.

Exactly same problem

goroutine 953 [running]:
github.com/pydio/cells/v4/common/utils/fork.(*Process).GetPID(...)
/source/common/utils/fork/process.go:84
github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe.func1.1()
/source/common/server/fork/fork.go:96 +0xbd7
github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe.func1()
/source/common/server/fork/fork.go:156 +0xa2
created by github.com/pydio/cells/v4/common/server/fork.(*Server).RawServe
/source/common/server/fork/fork.go:84 +0x3bd

OS: windows 7
upgrade to latest v4 within new installed cells 3.0.9

Thanks for your support !