X

xintersecty

Member

Last active 3 months ago

  1. 3 months ago
    Mon Jul 24 21:18:26 2017
    X xintersecty posted in Failure Web service/driver nic.

    We found the issue

    This was in the setup menu
    http://192.168.1.10/service/client.asmx

    What was needed
    http://192.168.1.10/clonedeploy/service/client.asmx

    I felt bad for missing this and it will cost be a bottle of Perrier.

  2. Mon Jul 24 16:23:24 2017
    X xintersecty posted in Failure Web service/driver nic.

    Going back to my own test setup, I tried the add computer service and got the same answer there too. So I don't think that is a related issue.

  3. Mon Jul 24 16:13:09 2017
    X xintersecty started the conversation Failure Web service/driver nic.

    So we setup a new clone deploy server. Using the proxy DHCP. Made sure the IP address is set correctly in the setup tab. 192.168.1.10 for the server as per the online instructions.

    We get this interesting error message
    Could Not Contact CloneDeploy Server. Possible Reasons:
    The CloneDeploy Web Service Is Not Functioning.
    Try Entering http://192.168.1.10/service/client.asmx/Test In A Web Browser.
    A Driver Could Not Be Found For This NIC.
    The Computer Did Not Receive An Ip Address.
    Press Enter To Continue

    So I did check the menu file to make sure it's pointing to the right IP address. After that did not work. I removed the security settings and generated a new SHA token. I updated the editor text file.

    We also used the TEST feature on webservices and the answer came back as "true"

    We also tried using the "add computer" and we got an error there. Please forgive me as this a eyeball type paste.

    Server Error in '/clonedeploy' Application
    The resource cannot be found
    Description: HTTP 404 The resources you are looking for ( or one of it's dependencies) could have been removed, had it's name changed, or temp. unavailable. Please review the following URL and make sure that it is spelled correctly.
    Requested URL: /clonedeploy/login.aspx

  4. 4 months ago
    Mon Jun 19 20:20:58 2017
    X xintersecty started the conversation Supporting Headless Systems.

    Some time ago I ran into issues with headless systems. A co-worker got it working (he installed the patch) and he understood the what was needed for GRUB. I am including them here to help the greater community.

    Configuration

    1. Install the latest patch (I do not know if it changes anything, but hey!)
    2. Go to “Admin” (cog icon) -> PXE.

    a. Using Proxy DHCP: No
    b. PXE Mode: grub
    c. Save
    3. Go to “Admin” (cog icon) -> Boot Menu -> ISO / USB Generator.
    a. Build type: ISO
    b. Kernel: 4.9.8x64 (comes with the patch)
    c. Boot Image: initrd.xz
    d. Kernel Arguments: console=tty0 vga=0 console=ttyS0,115200n8
    4. Go to “Admin” (cog icon) -> Boot Menu -> Default Menu.
    a. Kernel: 4.9.8x64 (comes with the patch)
    b. Boot Image: initrd.xz
    c. No username/password
    d. Create Boot Files
    5. Go to “Admin” (cog icon) -> Boot Menu -> Editor
    a. Add console=tty0 vga=0 console=ttyS0,115200n8 to all the kernel lines (see example below)
    b. Save Changes

    1. Go to “Images” and create a new image (linux, block)
    2. Once created, go to profiles (same “Images” section) and change the “default” profile with:

    a. PXE Boot Options:
    i. Kernel: 4.9.8x64
    ii. Boot Image: grub
    iii. Kernel Arguments: console=tty0 vga=0 console=ttyS0,115200n8
    iv. Save
    b. Task Options:
    i. Task Completed Action: Power Off
    ii. Save

    Default menu modifications

    insmod password_pbkdf2
    insmod regexp
    set default=0
    set timeout=10
    set pager=1
    regexp -s 1:b1 '(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3})' $net_default_mac
    regexp -s 2:b2 '(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3})' $net_default_mac
    regexp -s 3:b3 '(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3})' $net_default_mac
    regexp -s 4:b4 '(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3})' $net_default_mac
    regexp -s 5:b5 '(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3})' $net_default_mac
    regexp -s 6:b6 '(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3}):(.{1,3})' $net_default_mac
    mac=01-$b1-$b2-$b3-$b4-$b5-$b6

    if [ -s /pxelinux.cfg/$mac.cfg ]; then
    configfile /pxelinux.cfg/$mac.cfg
    fi

    menuentry "Boot To Local Machine" --unrestricted {
    exit
    }

    menuentry "Client Console" --user {
    echo Please Wait While The Boot Image Is Transferred. This May Take A Few Minutes.
    linux /kernels/4.9.8x64 root=/dev/ram0 rw ramdisk_size=156000 web=http://192.168.0.1/service/client.asmx/ USER_TOKEN=cd6beead-3802-43b0-9556-baa00bac379e task=debug consoleblank=0 console=tty0 vga=0 console=ttyS0,115200n8
    initrd /images/initrd.xz
    }

    menuentry "On Demand Imaging" --user {
    echo Please Wait While The Boot Image Is Transferred. This May Take A Few Minutes.
    linux /kernels/4.9.8x64 root=/dev/ram0 rw ramdisk_size=156000 web=http://192.168.0.1/service/client.asmx/ USER_TOKEN=cd6beead-3802-43b0-9556-baa00bac379e task=ond consoleblank=0 console=tty0 vga=0 console=ttyS0,115200n8
    initrd /images/initrd.xz
    }

    menuentry "Add Computer" --user {
    echo Please Wait While The Boot Image Is Transferred. This May Take A Few Minutes.
    linux /kernels/4.9.8x64 root=/dev/ram0 rw ramdisk_size=156000 web=http://192.168.0.1/service/client.asmx/ USER_TOKEN=cd6beead-3802-43b0-9556-baa00bac379e task=register consoleblank=0 console=tty0 vga=0 console=ttyS0,115200n8
    initrd /images/initrd.xz
    }

    menuentry "Diagnostics" --user {
    echo Please Wait While The Boot Image Is Transferred. This May Take A Few Minutes.
    linux /kernels/4.9.8x64 root=/dev/ram0 rw ramdisk_size=156000 web=http://192.168.0.1/service/client.asmx/ USER_TOKEN=cd6beead-3802-43b0-9556-baa00bac379e task=diag consoleblank=0 console=tty0 vga=0 console=ttyS0,115200n8
    initrd /images/initrd.xz
    }

  5. Mon Jun 19 19:26:30 2017
    X xintersecty posted in Failure to install 2012R2.

    Well, I removed the install and did it again, and BAM it worked. So I might have flubbed the install from the beginning. Now going through the upgrade process.

  6. Mon Jun 19 17:53:11 2017
    X xintersecty started the conversation Failure to install 2012R2.

    the application failed to start due to this error:

    -----------------------------

    Compilation Error
    Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

    Compiler Error Message: CS0234: The type or namespace name 'DirectoryServices' does not exist in the namespace 'System' (are you missing an assembly reference?)

    Source Error:

    Line 1: using System;
    Line 2: using System.DirectoryServices;
    Line 3: using Helpers;
    Line 4:

    Source File: c:\Program Files (x86)\clonedeploy\web\App_Code\BLL\Ldap.cs Line: 2
    ----------------------------

    My process

    1. Started with brand new IIS and server 2012R2
    2. Ran the installer
    3. I did do the path upgrade
    4. I then ran application

    I have attached the install log.

  7. 5 months ago
    Fri May 12 14:07:29 2017
    X xintersecty posted in Serial Console.

    Even with the new kernel I had not any luck. So we are putting this aside so we can get some other people look at our target. I suspect something is not being set right and passed to the loading kernel for our target Atom Board. Once we have a solution, I will come back here and update.

  8. Tue May 9 14:53:43 2017
    X xintersecty posted in Serial Console.

    The past couple of days I took a new tack and built a 4.11 kernel. I specified in the compile options there is no support for VGA and to user the serial console. The GRUB boot method works. So I have been booting into Diagnostic mode to see what is happening. It still goes into blind mode.

    GNU GRUB version 2.02~beta2-36ubuntu11

    /----------------------------------------------------------------------------\
    | Boot To Local Machine |
    | Client Console |
    | On Demand Imaging |
    | Add Computer |
    |*Diagnostics |
    | |
    | |
    | |
    | |
    | |
    | |
    | |
    | |
    \----------------------------------------------------------------------------/

    Use the ^ and v keys to select which entry is highlighted.
    Press enter to boot the selected OS, `e' to edit the commands
    before booting or `c' for a command-line.

    Please Wait While The Boot Image Is Transferred. This May Take A Few Minutes.
    error: no suitable video mode found.
    Booting in blind mode

    I suspect something in the configuration file from clonedeploy is causing too look for a unsupported video mode. My next testing step is to just boot my custom kernel on it's own.

  9. Fri May 5 17:34:02 2017
    X xintersecty posted in Serial Console.

    I added this to boot options
    vga=0 console=ttys0,115200

    I did verify boot grub and isolinux.cfg options were changed on the USB boot disk. Still no look, will continue to "just keep swimming"

    error: no suitable video mode found.
    Booting in blind mode

  10. Thu May 4 19:51:08 2017
    X xintersecty started the conversation Serial Console.

    Back again. So I decided to use the USB boot to troubleshooting booting on my device, Atom Board. So a couple of things I may not have mentioned, I am using a serial device for console I/O. We are running a sever version of Ubantu.
    I set the kernel Arguments to console=ttys0,115200.

    Grub works fine however once it starts booting in the OS, I get the following error and it goes into blind mode. I am not sure what that means. The serial sessions follows:

    B4
    error: no suitable video mode found.

    GNU GRUB version 2.02~beta2-9

    /----------------------------------------------------------------------------\
    | Boot To Local Machine |
    | Download Image |
    | Upload Image |
    |*Client Console |
    | Add Computer |
    | On Demand |
    | Diagnostics |
    | |
    | |
    | |
    | |
    | |
    \----------------------------------------------------------------------------/

    Use the ^ and v keys to select which entry is highlighted.
    Press enter to boot the selected OS, `e' to edit the commands
    before booting or `c' for a command-line. ESC to return previous
    menu.

    error: no suitable video mode found.
    Booting in blind mode

View more