We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The data.db file keeps getting corrupted and node crashes.
To Reproduce
** Steps to Restart Node **
Expected behavior The node should not drop
ERROR panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x140c7bc] goroutine 450 [running]: github.com/sentinel-official/dvpn-node/node.(*Node).jobUpdateSessions(0xc000e4c930) /go/src/github.com/sentinel-official/dvpn-node/node/jobs.go:109 +0x37c github.com/sentinel-official/dvpn-node/node.(*Node).Start.func3() /go/src/github.com/sentinel-official/dvpn-node/node/node.go:52 +0x1d created by github.com/sentinel-official/dvpn-node/node.(*Node).Start /go/src/github.com/sentinel-official/dvpn-node/node/node.go:51 +0x110
Coud Server (Linode):
Additional context Using Exidio APP on an Android Device to connect to Node for testing.
Exidio: V1.0.4 (Default DNS Handshake only) Phone: Samsung Galaxy A71 5G Android UI Version: 3.1 Android Version: 11 Google Play update: March 1st 2022 Baseband Version: A716U1UEU6DVA1 Kernel Version: 4.19.125-22734624 (sentinel-official/android-client-lite#1 Tue Jan 18 14:06:19 KST 2022) Build Number: RP1A.200720.012.A716U1UEU6DVA1 SE For Android Status: Enforcing SEPF_SM-A716U1_11_0010 (Tue Jan 18 14:06:19 2022) Knox Version: Know 3.7 API Level 33 TIMA 4.1.0 Security Version: MDF v3.1 Release 6 WLAN v1.0 Release 2 VPN Client v2.2 Rel 1.0 ASKS v4.5 R-20200806 ADP v3.0 R 20191001 FIPS BoringSSL v1.5 FIPS SKC v2.1 FIPS Scrypto v2.5 SMR Jan-2022 R 1
The text was updated successfully, but these errors were encountered:
Additional Note:
Every node that I connect to with Exidio on Android ends up with the data.db file corrupted.
I have a couple nodes that I have not connected to yet and they are still running without any downtime.
Q: Do you think there is something in the Exidio APP that could be corrupting the data.db file?
Sorry, something went wrong.
Attached is a copy of the corrupted data.db file. I changed the extension from .db to .txt so I could attach it here.
data-saved01.txt
I updated DVPN-Node to latest version v0.3.1. and I'm monitoring for the error.
bsrinivas8687
No branches or pull requests
Describe the bug
The data.db file keeps getting corrupted and node crashes.
To Reproduce
** Steps to Restart Node **
Expected behavior
The node should not drop
ERROR
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x140c7bc]
goroutine 450 [running]:
github.com/sentinel-official/dvpn-node/node.(*Node).jobUpdateSessions(0xc000e4c930)
/go/src/github.com/sentinel-official/dvpn-node/node/jobs.go:109 +0x37c
github.com/sentinel-official/dvpn-node/node.(*Node).Start.func3()
/go/src/github.com/sentinel-official/dvpn-node/node/node.go:52 +0x1d
created by github.com/sentinel-official/dvpn-node/node.(*Node).Start
/go/src/github.com/sentinel-official/dvpn-node/node/node.go:51 +0x110
Coud Server (Linode):
Additional context
Using Exidio APP on an Android Device to connect to Node for testing.
Exidio: V1.0.4 (Default DNS Handshake only)
Phone: Samsung Galaxy A71 5G
Android UI Version: 3.1
Android Version: 11
Google Play update: March 1st 2022
Baseband Version: A716U1UEU6DVA1
Kernel Version: 4.19.125-22734624 (sentinel-official/android-client-lite#1 Tue Jan 18 14:06:19 KST 2022)
Build Number: RP1A.200720.012.A716U1UEU6DVA1
SE For Android Status: Enforcing SEPF_SM-A716U1_11_0010 (Tue Jan 18 14:06:19 2022)
Knox Version: Know 3.7 API Level 33 TIMA 4.1.0
Security Version:
MDF v3.1 Release 6
WLAN v1.0 Release 2
VPN Client v2.2 Rel 1.0
ASKS v4.5 R-20200806
ADP v3.0 R 20191001
FIPS BoringSSL v1.5
FIPS SKC v2.1
FIPS Scrypto v2.5
SMR Jan-2022 R 1
The text was updated successfully, but these errors were encountered: