coredns container keeps restarting since install
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
@richard holst 5:30 works with me. Can you please email me credentials at waqar@ixsystems.com ? About the installation bit, this is desired behaviour and would remain like this in the future releases as well. Glad you like TN
Hi waqar,
I am avilable this wed from 6pm ...but only for about an hour ..till 7:15 pm ..I could maybe be vailable at 5:30pm to give us more time if your avilable ..not sure how much time you would need...
just on the package install situation ..I am going to look to run it in a container as thats my prefered option to most apps ..I was just wondering if this upgrade process will be the same in the final release or is this a test situation ?
just because I really excited that the OS is debian and I can make changes easily and I am curretly just running my NAS as a stock ubuntu machine where I install some things locally like netdata ..then the rest of the apps in containers
I also see this being my go to recomended NAS solution for family and friends as I am generally their in house support anything that makes things easier for me to support them and users easier to use I am thrilled by..
let me know ...richard
Thank you @richard holst for reaching back. Can you please confirm if 6pm Wednesday GMT time works with you ?
About the installed application, we don't expect new packages to be installed/configured other then the already available ones in the image we ship. And on upgrades, the complete BE is changed and the last one preserved which is why basically custom installations don't persist across upgrades. You can always use docker images or write a catalog item for this which will persist across upgrades and are officially supported
Hi waqar,
I am london based so gmt time zone ...in the evening would be best after 6pm onwards or between 8-9 am if the evenings dont work ..not sure what time zone you are on .. also do you want me to upload a debug file from the new instance ?
the first instace I did a lot of hacking of files etc to try fix the issue before loging the bug so it may not be the best example to use ..and I can even get the web interface to load currently ...I have tried loading an older build from the boot menu but its the same ..I was wondering if theres a way to to do a version update from the cli using the downloaded update file ? was wondering if that maybe fix the issues.
the second instace is more or less std build ...
I was wondering something you maybe able to quickly answer ...I have installed tailscale on my friends instance so i can remote connect and help him with things but everytime he upgrades the app disapears ? is that std or a apha build thing ? or am I doing something wrong installing it etc ..if you know please could you update me ...
regards
Richard
I have truenas scale installed on Vmware esxi VM with 2 Cpu and 16gb ram ...
I am on the nightly build and I upgrade every few days ...problem has not resolved after at least 5 version updates
I have the k3s running but since install the coredns container just keeps restarting and never comes up ...the other services all start fine.
I have tried a number of K3s solutions but they did not make any differance or were just not an option due to the custom install ...
I could just blow the install away and start again but I would prefer to fix the issue encase this happens in production at a later stage.
this is my first time working with kubernetes but I have been using docker for a few years
I am not sure what logs etc would be useful to problem solve this issue but here is the container logs out put ...
hn-trnas-1# kubectl logs coredns-854c77959c-nv5n4 -n kube-system
.:53
[INFO] plugin/reload: Running configuration MD5 = 442b35f70385f5c97f2491a0ce8a27f6
CoreDNS-1.8.0
linux/amd64, go1.15.3, 054c9ae
hn-trnas-1# kubectl logs coredns-854c77959c-nv5n4 -n kube-system
.:53
[INFO] plugin/reload: Running configuration MD5 = 442b35f70385f5c97f2491a0ce8a27f6
CoreDNS-1.8.0
linux/amd64, go1.15.3, 054c9ae
[INFO] SIGTERM: Shutting down servers then terminating