Hi @oleorhagen,
Im facing this lke I mentioned 2 days back, One of my deployment is failed and current software I can see “Inconsistent”, after this Mender deployment isnt happening, deploy is stuck in ‘pending. Why all this happening, device type and every detail is fine.
No, this is a feature ticket.
Im very sorry @oleorhagen, I couldtn reply u sooner. What is this ticket, I can see its open, and this is what Im looking for I guess, Still I couldnt resolve it, Im not able to deploy any further releases to the device because of a past failure deployment and causing it to be "Inconsistent " artifact. I think I’ll have only one option to decommision, But even after decommission, no change. 
Hi @nishad1092.
From what I understand the device should still be able to take a new update.
What exactly is the script doing? Is trying to reboot?
Hi @oleorhagen, Im using dir module to deploy a directory of two python files, and its done, and further execute the python file using .sh script module. And it fails for some reason, Even if it fails , it shouldnt cause these many issues right, The Entire mender is slow, and freezy, and now can’t deploy update to taht device also.
Could you post a deployment log here?
all the logs are gone when I decommisioned it. Well, let me try to get it and Ill share it here sooner.
Hi, Could you genuinely tell me, If I power up a production server, will it be smoother than the Demo server I have now?
Tell me please, So I can confidently say No to Demo server, Because Im trying to evaluating this platform. Have u faced these issues in Demo server. Even the server GUI is freezy and stuck mate.
No.
Honestly, I have never encountered any of these issues. Or heard about a single person having this many issues.
Obviously, I cannot make any guarantees as to the quality of the production setup for you, since you been having a lot of issues with the setup that is unfamiliar to me. Especially the GUI freeze.
I even gave the demo a try locally just now, and it works just fine for me. Both locally on my desktop, and on a lower-powered setup I have at home.
We have even done scale-testing of this previously, with tens of thousands of devices, and still no GUI freeze.
If you are to receive any fruitful feedback from us on these issues you are having you need to provide the information that is needed in order for us to reproduce this, otherwise there is no way we can help you with this.
That is information on machine, OS, commands you’ve run. Logs, statistics and observations, etc.
Sure @oleorhagen Ill be happy to provide you with any logs or info.
Okay, since you have clarified on my issues are very unfamiliar, I will setup the demo server once again in a new server with sufficient requirements, and if it again occurs then we can take it further with “why” and "how to resolve it " rgt?
Let me setup a new server of Demo version. I hope all these issues wont occur again. Wow, You just mentioned thousand of devices in a demo server? but they have mentioned only 500, How to get few more ?
I would really like to thank you for all these responses, I’m really looking into Mender, I want this to work, Mender looks very interesting !!
Hi @oleorhagen,
I have setup the production server. It looks good, Our past communication has helped me alot to reach here.
Now, I’m trying to figure out how to get Mender devices to connect to server.
For demo server, it was extremly easy to configure Mender client to server communication, but for production, I’m not able to start where in the documentation.
Because from what I read, it has lots of configuration needed, therefore Im worried how will i manage it for 100’s or 1000’s devices for production while manufacturing it, I need mender clients during the manufacturing time (or Is it possible to automate the config) . When it comes to demo server the config was just so easy, just run the shell commends:
DEVICE_TYPE=“jetsonnano”
SERVER_IP_ADDR=“4…/.xx.xxx.xxx”
sudo DEBIAN_FRONTEND=noninteractive dpkg -i mender-client_2.2.0-1_arm64.deb
sudo mender setup
–device-type $DEVICE_TYPE
–demo
–server-ip $SERVER_IP_ADDR
sudo systemctl restart mender-client
mender setup --help will show the options available. You can remove the “–demo” parameter and add the “–server-url” parameter.
Hi @drewmoseley,
That is very resourceful info. Can we also include server.crt and modify mender.conf as a parameter ?
You can include the server.crt as a command line parameter. Most of the command line parameters end up modifying the mender.conf file but there may still be settings you want to tweak manually after you have generated the basic configuration.
Sure Drew, Ill give a try to configure server.crt and server URL through the command line parameter once and get back to you.
