/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Dear,

Since we changed a file in +- 7 images users can't deploy images on our remote site. They get the error "Image deployment failed: Internal error (8)" What is the reason for this? And it would also be nice to see a list of error codes so we know what is wrong in the future.

What i have done:
1. replaced the files (sylink.xml replaced because of a symantec server migration)
2. applied changes to manifest
3. synced the remote site

didn't work so:

1. rebooted the remote site
2. synced again

didn't work so:
1. tried to image a pc at our office, no problems.

I'm stuck here.. It seems that the remote site is bugging, but there was no problem before.


Annyone knows a solution?

Greetz

Edit: Added picture of a random image. (Although it worked fine before..)

0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
Has the RSA synced? Is there anything in the logs, particularly the privileged action output/error logs?

What version of KBOX and RSA are you on?
Answered 11/17/2009 by: jkatkace
Purple Belt

Please log in to comment
0
Hi,

Kbox 2000 says the RSA has synced succesfully.

I did found this in the logs:running /kbox/bin/configure_node_pxelinux.php 491
KSudoServer[21093] @ Wed, Nov 18 2009 09:08:08 CET: command exit status is 0
KSudoServer[21093] @ Wed, Nov 18 2009 09:08:08 CET: command produced no output
KSudoServer[844] @ Wed, Nov 18 2009 09:08:08 CET: cleaning up child process 21093
KSudoServer[21138] @ Wed, Nov 18 2009 09:08:14 CET: running /kbox/bin/configure_node_pxelinux.php 456
KSudoServer[21138] @ Wed, Nov 18 2009 09:08:14 CET: command exit status is 0
KSudoServer[21138] @ Wed, Nov 18 2009 09:08:14 CET: command produced no output
KSudoServer[844] @ Wed, Nov 18 2009 09:08:14 CET: cleaning up child process 21138
KSudoServer[21184] @ Wed, Nov 18 2009 09:08:20 CET: running /kbox/bin/configure_node_pxelinux.php 84
KSudoServer[21184] @ Wed, Nov 18 2009 09:08:20 CET: command exit status is 0
KSudoServer[21184] @ Wed, Nov 18 2009 09:08:20 CET: command produced no output
KSudoServer[844] @ Wed, Nov 18 2009 09:08:20 CET: cleaning up child process 21184
KSudoServer[21255] @ Wed, Nov 18 2009 09:08:26 CET: running /kbox/bin/configure_node_pxelinux.php 661
KSudoServer[21255] @ Wed, Nov 18 2009 09:08:26 CET: command exit status is 0
KSudoServer[21255] @ Wed, Nov 18 2009 09:08:26 CET: command produced no output
KSudoServer[844] @ Wed, Nov 18 2009 09:08:26 CET: cleaning up child process 21255
KSudoServer[21302] @ Wed, Nov 18 2009 09:08:32 CET: running /kbox/bin/configure_node_pxelinux.php 328
KSudoServer[21302] @ Wed, Nov 18 2009 09:08:32 CET: command exit status is 0
KSudoServer[21302] @ Wed, Nov 18 2009 09:08:32 CET: command produced no output
KSudoServer[844] @ Wed, Nov 18 2009 09:08:32 CET: cleaning up child process 21302
KSudoServer[21351] @ Wed, Nov 18 2009 09:08:38 CET: running /kbox/bin/configure_node_pxelinux.php 325
KSudoServer[21351] @ Wed, Nov 18 2009 09:08:38 CET: command exit status is 0
KSudoServer[21351] @ Wed, Nov 18 2009 09:08:38 CET: command produced no output
KSudoServer[844] @ Wed, Nov 18 2009 09:08:38 CET: cleaning up child process 21351
KSudoServer[21400] @ Wed, Nov 18 2009 09:08:44 CET: running /kbox/bin/configure_node_pxelinux.php 330
KSudoServer[21400] @ Wed, Nov 18 2009 09:08:44 CET: command exit status is 0
KSudoServer[21400] @ Wed, Nov 18 2009 09:08:44 CET: command produced no output
KSudoServer[844] @ Wed, Nov 18 2009 09:08:44 CET: cleaning up child process 21400

Somehow that started when i logged in this morning. Because when i first checked it there was nothing in the log, 30mins later it says "[KAMCE_WedAMCETE_0+01000] [krotate] [16871] logfile turned over
"


And im on version "3.0.25580" for the k2100 and the RSA is on "Current Version: 3.0.25214" (latest versions by kace).
Answered 11/18/2009 by: wesjuhdabomb
Orange Belt

Please log in to comment