https://netmaker.org logo
Powered by
Hmm, tried to update netclient to 1.14.6 on Window...
# client
f
Hmm, tried to update netclient to 1.14.6 on Windows, but now the service fails due to "Error 1067: The process terminated unexpectedly"
q
i think when that happened to me, i opened a cmd or powershell prompt and ran netclient manually to check for errors
service wouldn't start because something needed fixing first
f
Can't see any errors etc... in the windows event viewer I only see: * Starting netclient.exe daemon * Service started successfully * Child process [14360 - netclient.exe daemon] finished with 1 šŸ¤”
running netclient pull --vvv through cmd/powershell doesn't throw any errors at all
q
tried doing a 'netclient uninstall' then 'netclient install' again?
j
can you run "netclient.exe daemon" from the command line and see what error you get?
f
Copy code
C:\Program Files (x86)\Netclient>netclient daemon
[netclient.exe] 2022-07-27 22:47:51 netclient.exe is in proper location, C:\Program Files (x86)\Netclient\netclient.exe
2022/07/27 22:47:51 Gravitl Netclient on Windows started
[netclient.exe] 2022-07-27 22:47:51 [daemon.go-46] Daemon(): netclient daemon started -- version: v0.14.6
[netclient.exe] 2022-07-27 22:47:51 [clientconfig.go-22] UpdateClientConfig(): checking for netclient updates...
[netclient.exe] 2022-07-27 22:47:51 [clientconfig.go-48] UpdateClientConfig(): finished updates
2022/07/27 22:47:51 pid tracking not supported on windows
j
does the process terminate after that?
f
Yup
j
ok, that's a bug then, the pid tracker is new. It's not supposed to get applied to windows but looks like it is
I'm adding it to our internal tracker to fix, but it's probably worth creating a github issue as well.
f
Alright. I can create one
Nice work with the quick hotfix šŸ™‚ replaced the netclient.exe with the new one and the service started without the error. I did however see
Copy code
[netclient.exe] 2022-07-28 00:24:51 [mqhandlers.go-202] UpdatePeers(): server/client version mismatch server:  v0.14.6  client:
in the winsw.out.log file. Is that something to worry about or just info? šŸ™‚
b
Info message for now
j
netclient.exe created by the workflow is missing version. We need to manually build and replace. I am out right now but will upload when im back
h
I have tried to update all my nodes to 14.6 today, but the windows nodes are all failing. Current version is N/A in the UI and the log file says there is a mismatch between server and client, OS not supported. This is with the exe and the MSI downloaded moments ago. Stopped services and replaced binary, also tried leaving network, uninstalling, removing services, reinstalling MSI and replacing exe again but all the same result. Also, I still have warnings on downloading binaries and installers and in windows I have to manually run the exe to get it passed windows smart screening
Linux nodes all happy of course
b
h
saw that, thanks. but the hotfix doesn't seem to have worked for me. oddly, the netclient service is running on my machines
WTF? netclient -v gives Netclient CLI version v0.12.0!
No way I scrolled down releases and downloaded that one !
Yep, I'm getting v 12.0 downloading the exe from 14.6
OMG, my brain
At least it makes everything I mentioned above make sense @bored-island-21407. Would you have time to take a look? Otherwise I need to start rolling stuff back pretty quickly
b
need @jolly-london-20127, I don't do windows.
h
hehe, ok
wish I didn't either
b
h
Interesting, half the size
Trying it now
b
built on linux
h
That's not happy
b
too bad, I tried
h
It's looking in ProgramData where it used to be several versions back
Thanks though!
Oh tis hurting now. so netclient -v give me Netclient CLI version v0.12.0
This because it's looking and finding an old version in system32 šŸ˜«
.\netclient -v with 0.14.5 gives Gravitl Netclient on Windows started Netclient version v0.14.5 as expected
but .netclient -v doesn't work with 0.14.6, which is what promted me to use only netclient -v (without the .\), returning an older version. This old stuff may be related to my issues though. I'll keep investigating
Back with 0.14.6 client, the version in the UI now shows as 'dev'
b
that is default if ldflag is not passed when building --- for some unknown reason when building the windows variant, the ldflag is ignored sometimes
j
hold on a bit, I just haven't uploaded the hotfixed version yet, and the workflow replaced the existing one with a faulty version
h
OK, thanks. I thought @few-airline-95046 said it was there already
j
yeah the new version is there, but the way it builds it, the version is missing, which pellen showed in their logs too
h
Yeah, that seems to be making it very cross on my end
j
ok, binary has been updated @handsome-lifeguard-70799 @few-airline-95046
h
Lookin good!
No errors in my logs
5 Views
PreviousNext
Powered by