Last active 4 months ago

  1. 4 months ago
    Fri Apr 27 19:28:52 2018

    Made it permanent and all is well... Thanks for all the help!

  2. Fri Apr 27 18:59:15 2018

    It sure enough is!!! Don't know how I missed that.... twice!
    setenforce permissive and we're good to go!!

  3. Fri Apr 27 18:47:32 2018

    deleted error_log and rebooted, then tried twice to connect:

    [Fri Apr 27 13:43:35.293736 2018] [core:notice] [pid 1052] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
    [Fri Apr 27 13:43:35.604832 2018] [suexec:notice] [pid 1052] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Fri Apr 27 13:43:35.662738 2018] [auth_digest:notice] [pid 1052] AH01757: generating secret for digest authentication ...
    [Fri Apr 27 13:43:35.664340 2018] [lbmethod_heartbeat:notice] [pid 1052] AH02282: No slotmem from mod_heartmonitor
    [Fri Apr 27 13:43:35.727984 2018] [mpm_prefork:notice] [pid 1052] AH00163: Apache/2.4.6 (CentOS) mod_mono/3.13 configured -- resuming normal operations
    [Fri Apr 27 13:43:35.728122 2018] [core:notice] [pid 1052] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
    [Fri Apr 27 13:45:08.164462 2018] [:error] [pid 1242] Failed to connect to mod-mono-server after several attempts to spawn the process.
    [Fri Apr 27 13:45:41.409199 2018] [:error] [pid 1244] Failed to connect to mod-mono-server after several attempts to spawn the process.
  4. Fri Apr 27 18:12:51 2018

    I created a 'default.htm' in the root of /var/www/html/ and I can navigate to it no problem (http://<server_ip>/default.htm).... I just can't get to the sub-web (I thinks that's what it's called) of clonedeploy.

  5. Fri Apr 27 18:01:42 2018

    Tried again and replaced apache2 with httpd in the following line:
    yum -y install mono-devel apache2-mod_mono apache2 httpd udpcast lz4 mkisofs wget

    Same results:
    503 Service Unavailable

  6. Fri Apr 27 14:59:41 2018
    J jcargile posted in Can't Image an x86 Laptop.

    Well good-night.... that was easy enough!

  7. Fri Apr 27 14:48:22 2018

    Ok.... I'll revert and try again. Thanks for the info

  8. Fri Apr 27 14:36:04 2018

    Should be 'httpd' instead of 'apache2'?

  9. Fri Apr 27 14:33:38 2018
    J jcargile posted in Can't Image an x86 Laptop.

    I have tried re-generating the boot menu files so that the kernel section is bitness agnostic:
    kernel kernels\4.13.2

    Before re-generating, the boot menu (in the clonedeploy boot menu editor) was showing:
    kernel kernels\4.13.2x64

    I even removed the computer and re-registered it, but when I try to do an upload, all I get is:
    "Loading kernels\4.13.2x64.... ok"
    "Loading images\initrd.xz... ok"
    and then the same error:
    "This kernel requires an x86-64 CPU, but only detected an i686 CPU."
    "Unable to boot..."

  10. Fri Apr 27 01:57:59 2018
    J jcargile started the conversation Can't Image an x86 Laptop.

    I installed CloneDeploy on a Windows 7 x64 VM just for testing.
    Set my existing DHCP Server to the correct parameters to instruct clients to PXE boot.
    Set a couple of clients to PXE boot.
    Worked like a charm!!! I can 'upload' an image from a VM and from hardware running Windows 10...
    ... as long as they are 64-bit!!!
    Tried to upload from an x86 laptop and I get nothing but errors:
    Something about "expected x64 but found i686 instead"
    Tried messing with boot menus but still getting the same error

View more