Results 1 to 8 of 8

Thread: Appliance Beta5 issues

  1. #1
    Join Date
    Jul 2012
    Posts
    1
    Rep Power
    3

    Default Appliance Beta5 issues

    Griaß di!

    I downloaded the beta-OVA zca-8.0.0.0-116_OVF10.ova and installed on vSphere5 Hypervisor (free edition).
    After deploying the OVA, the VM starts normaly (i thought), and the "welcome screen" is displayed in the console.
    Screen says that all IPs are 127.0.0.1
    OK - lets change in the appropriate system file. Done - works (i'm very proud of this, 'cause i am a windows guy...).
    After a little testing i shutted down the VM for holidays.
    Started the Vm after my holidays, all IP changes are gone.

    Let's search for information...
    In the forum i found this post http://www.zimbra.com/forums/install...tml#post244849 with the network properties screenshot.
    During the deploymant of the OVA i never was asked for the IP configuration.
    I tried a new deployment, but no screen for the IP config.

    Did i miss something?

  2. #2
    Join Date
    Nov 2005
    Location
    Germany
    Posts
    89
    Rep Power
    9

    Default

    Nope, same here!
    ---
    Ubuntu 12.04 - Release 8.0.2.GA.5569.UBUNTU12.64 UBUNTU12_64 FOSS edition. - z-push

  3. #3
    Join Date
    Jul 2006
    Posts
    623
    Rep Power
    10

    Default

    The IP configuration prompts only appear when deploying against vCenter. The IP address reverting vSphere, Workstation and Fusion is addressed in the GA release which will be out shortly.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  4. #4
    Join Date
    Aug 2012
    Posts
    4
    Rep Power
    3

    Default

    This was not addressed as of: 8.0.0 GA Release (zca-8.0.0.0-1147_OVF10.ova)

    I just installed today on vSphere Server (Img: ESXi-5.0.0-20120302001-standard) using vSphere Client 5.0.0 (Build: 623373) and still no method to set or configure the network settings.

    All IP's on the "initial configuration and virtual appliance managment interface" (start-up blue screen) are set to 127.0.0.1

    Any attempts to configure the network (i.e. Select Login at the blue screen and run: /opt/vmware/share/vami/vami_config_net) are OVERWRITTEN once the VM restarts.

    As far as I can tell, there has been no solution or fix for this. I've been searching / troubleshooting / trying things going on 6 hours now (today) and nothing useful yet.

  5. #5
    Join Date
    Sep 2012
    Posts
    2
    Rep Power
    3

    Default ovfenv

    Could you please execute ovfenv at the console and attach the output here ?

    Also, please attach the log file /opt/vmware-zca-installer/zca-fixhosts.log content.

    We have verified that this works, but we would like to see if this is a different kind of a problem.

    Quote Originally Posted by Tim.iTelework View Post
    This was not addressed as of: 8.0.0 GA Release (zca-8.0.0.0-1147_OVF10.ova)

    I just installed today on vSphere Server (Img: ESXi-5.0.0-20120302001-standard) using vSphere Client 5.0.0 (Build: 623373) and still no method to set or configure the network settings.

    All IP's on the "initial configuration and virtual appliance managment interface" (start-up blue screen) are set to 127.0.0.1

    Any attempts to configure the network (i.e. Select Login at the blue screen and run: /opt/vmware/share/vami/vami_config_net) are OVERWRITTEN once the VM restarts.

    As far as I can tell, there has been no solution or fix for this. I've been searching / troubleshooting / trying things going on 6 hours now (today) and nothing useful yet.

  6. #6
    Join Date
    Aug 2012
    Posts
    4
    Rep Power
    3

    Default

    Results of: ovfenv
    --
    root@mail103:~# ovfenv
    Unable to find the ovf environment.
    --

    zca-fixhosts.log repeats the same few lines, and since I couldn't get attachment to work, I will just paste a few iterations of the repeated log entries:

    root@mail103:~# cat /opt/vmware-zca-installer/zca-fixhosts.log
    Tue Jul 10 22:41:20 UTC 2012 : debug started
    Tue Jul 10 22:41:21 2012 :Starting zca-set-network script
    zca_ip=127.0.0.1
    zca_netmask=255.255.255.0
    zca_gateway=default
    Updating network with 127.0.0.1 255.255.255.0 default
    Tue Jul 10 22:41:21 2012one.
    Tue Jul 10 22:41:21 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killing dhcp client.
    Tue Jul 10 22:41:21 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killed dhcp clients.
    Tue Jul 10 22:41:21 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts updating /etc/hosts.
    Thu Sep 13 16:45:10 UTC 2012 : debug started
    Thu Sep 13 16:45:28 2012 :Starting zca-set-network script
    zca_ip=127.0.0.1
    zca_netmask=255.255.255.0
    zca_gateway=default
    Updating network with 127.0.0.1 255.255.255.0 default
    Thu Sep 13 16:45:28 2012one.
    Thu Sep 13 16:45:28 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killing dhcp client.
    Thu Sep 13 16:45:28 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts killed dhcp clients.
    Thu Sep 13 16:45:28 UTC 2012 : Zimbra Collaboration Appliance zca-fixhosts updating /etc/hosts.
    Thu Sep 13 10:18:54 PDT 2012 : debug started
    Thu Sep 13 10:19:12 2012 :Starting zca-set-network script
    zca_ip=127.0.0.1
    zca_netmask=255.255.255.0
    zca_gateway=default
    Updating network with 127.0.0.1 255.255.255.0 default
    Thu Sep 13 10:19:12 2012one.
    Thu Sep 13 10:19:12 PDT 2012 : Zimbra Collaboration Appliance zca-fixhosts killing dhcp client.
    Thu Sep 13 10:19:12 PDT 2012 : Zimbra Collaboration Appliance zca-fixhosts killed dhcp clients.
    Thu Sep 13 10:19:12 PDT 2012 : Zimbra Collaboration Appliance zca-fixhosts updating /etc/hosts.
    Last edited by Tim.iTelework; 09-17-2012 at 04:29 PM.

  7. #7
    Join Date
    Aug 2012
    Posts
    4
    Rep Power
    3

    Default

    After poking around in /opt/vmware-zca-installer/bin/zca-fixhosts, I can see that it does a lot of editing of the network config AND runs on start-up. Most likely this is the culprit.

    I also found: /opt/vmware/share/vami/vami_get_network

    Which results in:
    ------------
    root@mail103:~# /opt/vmware/share/vami/vami_get_network
    interface: eth0
    config_present: true
    config_flags: STATICV4
    config_ipv4addr: 127.0.0.1
    config_netmask: 255.255.255.0
    config_broadcast: 127.0.0.255
    config_gatewayv4:
    config_ipv6addr:
    config_prefix:
    config_gatewayv6:
    autoipv6:
    active_ipv4addr: My.Correct.Internal.IP
    active_netmask: 255.255.255.0
    active_broadcast: My.Correct.B.Cast
    active_ipv6addr:
    active_prefix:
    active_gatewayv4: My.Correct.Gateway.IP
    active_gatewayv6:
    hasdhcpv6: 0
    managed: Managed Internally
    ------------

    I will try to disable / configure correctly some how!

  8. #8
    Join Date
    Sep 2012
    Posts
    2
    Rep Power
    3

    Default

    Hi,

    Sorry for late response. But can you please do these steps.

    1) clear the log file zca-fix-hosts.log

    2) re-configure the network with /opt/vmware/share/vami/vami_config_net

    3) re-boot the appliance.

    4) and please send us the log file and also check whether the network parameters stayed.

    Some how the network parameters did not get set correctly. If the OVFENV says nothing available,
    we won't fix any network stuff.

Similar Threads

  1. Zimbra 8 Appliance Beta 5 installation issues
    By senaz in forum Installation
    Replies: 0
    Last Post: 08-07-2012, 04:40 PM
  2. Replies: 1
    Last Post: 07-25-2012, 12:38 AM
  3. Update beta5 crashed
    By abdurs in forum Error Reports
    Replies: 6
    Last Post: 12-11-2008, 10:23 PM
  4. Replies: 2
    Last Post: 07-02-2007, 05:56 AM
  5. VMWare appliance issues
    By z3rum in forum Installation
    Replies: 9
    Last Post: 05-25-2006, 10:08 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •