ClientImaging web service not functioning
-
CloneDeploy worked on a similar setup without issue.
-
Is the booted linux trying to connect to the database on port 3306 and that's why it's having problems, or is there a service that it can't reach that needs to be turned on or allowed in the firewall? What is the test that it tells me to run?
Saying it needs to be on a dedicated pc is not an acceptable answer. Tell me how to get past this obstacle on this pc.
-
I'm sorry your having trouble getting this setup properly. We have support plans available if you need further assistance.
-
@theopenem_admin Wow........
-
How else would you expect me to react? Your previous post is are uncalled for. This is free software, you should show more respect and not demand things.
Saying it needs to be on a dedicated pc is not an acceptable answer. Tell me how to get past this obstacle on this pc.
An attitude lilke this won't get you far. If your ready to be more respectful, I can try and help you, otherwise, so long and good luck.
-
What would I expect?
I would expect someone who writes software to try and get as much information about something that is going wrong with their software so as to be able to fix it. I wanted to let you know about all of the problems I had with this to help you fix the bugs so your product could be better. I love clonedeploy and wanted to love this and help it be better, but you seem more interested in selling me support than making your product better.
So, if you decide to help or not, that doesn't bother me in the slightest. I'll go look elsewhere for something that meets my needs. I love the opensource community and want to help it grow, but not with people who aren't interested in building the community.
-
@jabeavers said in ClientImaging web service not functioning:
Is the booted linux trying to connect to the database on port 3306 and that's why it's having problems, or is there a service that it can't reach that needs to be turned on or allowed in the firewall? What is the test that it tells me to run?
It doesn't matter what database the port runs on. The imaging client is not connecting to the database, just the api. When your imaging client fails to contact the server, there is a message asking you to try and connect with a url from your web browser. What do you get if you try that?
-
@theopenem_admin I don't know what url to try, as the message does not say. Can you supply the url to try for testing?
Thanks.
-
It's different for everyone. Can you post a screenshot of the error, perhaps I'm not following where things are going wrong?
-
@theopenem_admin I'm not on campus right now, so I can't supply a screenshot.
Could it be a blocked port in a firewall? I remember a testing url in your documentation for testing that would return "60". Should I try that url from the computer I'm trying to network boot?
-
It's most likely an issue with your pxe boot files. You say you generated them yourself, they are probably missing some parameters. The better option be would be to determine why they aren't generating. You would need to supply all of the server logs as mention here.
https://docs.theopenem.com/tutorials/logs/ -
@theopenem_admin Okay. I will when I am able.
Thank you.
-
Here's the application log. It says something about the boot menu....
-
This is going to be difficult to troubleshoot, since it didn't even install properly. When you generate the boot menus is the kernel dropdown populated or empty?
-
@theopenem_admin the kernel dropdown is populated. At first, when I tried downloading new kernels it failed, but when I set the correct com unique ID it worked and I can see the kernel it downloaded in the correct directory.
-
Have you tried using the usb boot method? Does it show a different error, that may help pinpoint the issue.
-
@theopenem_admin no, but I will do so now.
Thanks
-
I just generated an iso and tried to mount it and Windows said the image is corrupted.
-
I tried using the generated iso and it just switched to the network boot instead. Is that what it's supposed to do?
-
No, it seems like your installation might be missing some required files. Do you know exactly where it stopped?