Hey Evan,
Usually this problem is indicative of a failure early in the startup
scripts inside the zone. Unfortunately, vmadm can't provide you with too
much information about what's going on here, because it's happening inside
the zone. As Ian mentions, this is usually caused by a bad networking
configuration getting in the way of the startup scripts that want to access
the internet. If this isn't the case here, though, you'll need to determine
what's failing in the zone. You could try running something like the
following before creating the zone:
dtrace -n 'proc:::exec-success /zonename != "global"/ { printf("%s execed
in %s", execname, zonename); }' -n 'fbt:genunix:exit:entry /zonename !=
"global"/ { printf("%s exited with %d in %s", execname, args[1], zonename);
}'
Hopefully this way you can get an idea of what processes are being started
and exiting non-zero in the zone.
- Cody
On Thu, Nov 26, 2015 at 6:33 PM, Evan Rowley <[email protected]> wrote:
> Here are some logs which were generated when a vmadm create command timed
> out while creating an LX zone:
>
> less /var/svc/log/system-smartdc-vmadmd\:default.log
>
> ...
>
> {"name":"vmadmd","req_id":"40f46435-83f2-c144-9b0b-837dce03c577","hostname":"00-25-90-b5-25-a8","pid":3506,"action":"load","vm":"cfc66d03-dbb3-4548-8
> da9-8e58643ab22e","level":20,"msg":"loading zonexml_objects took 17
> ms","time":"2015-11-27T02:17:56.380Z","v":0}
> {"name":"vmadmd","req_id":"40f46435-83f2-c144-9b0b-837dce03c577","hostname":"00-25-90-b5-25-a8","pid":3506,"action":"load","vm":"cfc66d03-dbb3-4548-8da9-8e58643ab22e","level":20,"msg":"loading
> last_exited took 1 ms","time":"2015-11-27T02:17:56.381Z","v":0}
> {"name":"vmadmd","req_id":"40f46435-83f2-c144-9b0b-837dce03c577","hostname":"00-25-90-b5-25-a8","pid":3506,"action":"load","vm":"cfc66d03-dbb3-4548-8da9-8e58643ab22e","level":40,"msg":"\"exit_status\"
> requested, but not found in cache for VM
> cfc66d03-dbb3-4548-8da9-8e58643ab22e","time":"2015-11-27T02:17:56.382Z","v":0}
> {"name":"vmadmd","req_id":"40f46435-83f2-c144-9b0b-837dce03c577","hostname":"00-25-90-b5-25-a8","pid":3506,"action":"waitForProvisioning","vm":"cfc66d03-dbb3-4548-8da9-8e58643ab22e","level":20,"transition_expire":1448590975012,"now":1448590676383,"msg":"waiting
> 298.629 sec(s) for provisioning","time":"2015-11-27T02:17:56.383Z","v":0}
> {"name":"vmadmd","req_id":"40f46435-83f2-c144-9b0b-837dce03c577","hostname":"00-25-90-b5-25-a8","pid":3506,"action":"waitForProvisioning","vm":"cfc66d03-dbb3-4548-8da9-8e58643ab22e","level":20,"msg":"setting
> provision timeout for
> cfc66d03-dbb3-4548-8da9-8e58643ab22e","time":"2015-11-27T02:17:56.384Z","v":0}
> {"name":"vmadmd","req_id":"40f46435-83f2-c144-9b0b-837dce03c577","hostname":"00-25-90-b5-25-a8","pid":3506,"action":"waitForProvisioning","vm":"cfc66d03-dbb3-4548-8da9-8e58643ab22e","level":20,"msg":"created
> watcher for
> cfc66d03-dbb3-4548-8da9-8e58643ab22e","time":"2015-11-27T02:17:56.385Z","v":0}
> {"name":"vmadmd","hostname":"00-25-90-b5-25-a8","pid":3506,"level":20,"msg":"still
> waiting for cfc66d03-dbb3-4548-8da9-8e58643ab22e to complete provisioning,
> ignoring additional transition.","time":"2015-11-27T02:17:56.695Z","v":0}
> {"name":"vmadmd","hostname":"00-25-90-b5-25-a8","pid":3506,"level":20,"msg":"still
> waiting for cfc66d03-dbb3-4548-8da9-8e58643ab22e to complete provisioning,
> ignoring additional transition.","time":"2015-11-27T02:17:56.754Z","v":0}
> {"name":"vmadmd","req_id":"40f46435-83f2-c144-9b0b-837dce03c577","hostname":"00-25-90-b5-25-a8","pid":3506,"action":"waitForProvisioning","vm":"cfc66d03-dbb3-4548-8da9-8e58643ab22e","level":40,"msg":"Marking
> VM cfc66d03-dbb3-4548-8da9-8e58643ab22e as a \"failure\" because we hit
> waitForProvisioning() timeout.","time":"2015-11-27T02:22:55.014Z","v":0}
>
>
> I suppose my next steps are to learn NodeJS, find the code meant to be
> executed when waitForProvisioning() is called, then try to reason why that
> unknown code isn't telling vmadm that an LX zone is provisioned.
>
>
>
> On Thu, Nov 26, 2015 at 9:22 PM, Evan Rowley <[email protected]>
> wrote:
>
>> Yes. The gateway is pingable. The IP isn't a duplicate of anything else
>> on the same subnet. The netmask is 255.255.255.248, and doesn't seem like
>> it should be an issue.
>>
>> On Thu, Nov 26, 2015 at 4:23 PM, Ian Collins <[email protected]> wrote:
>>
>>> Evan Rowley wrote:
>>>
>>>> Hello,
>>>>
>>>> vmadm is hanging when creating LX zone using the lxtest JSON shown on
>>>> the Getting Started steps of the wiki, last edited Oct 08, 2015.
>>>>
>>>> Link:
>>>> https://wiki.smartos.org/display/DOC/LX+Branded+Zones
>>>>
>>>>
>>>> I successfully ran:
>>>>
>>>> # imgadm import 52be84d0-6b06-11e5-a4c0-9f0c52fa368a
>>>>
>>>> Created the following JSON file, lxtest.json, with appropriate values
>>>> for <ip>, <netmask>, and <gw>.
>>>>
>>>> {
>>>> "alias": "lxtest",
>>>> "brand": "lx",
>>>> "kernel_version": "3.13.0",
>>>> "max_physical_memory": 2048,
>>>> "image_uuid": "52be84d0-6b06-11e5-a4c0-9f0c52fa368a",
>>>> "resolvers": ["8.8.8.8","8.8.4.4"],
>>>> "nics": [
>>>> {
>>>> "nic_tag": "admin",
>>>> "ip": "<ip>",
>>>> "netmask": <netmask>",
>>>> "gateway": "<gw>",
>>>> "primary": true
>>>> }
>>>> ]
>>>> }
>>>>
>>>>
>>> Are your nic parameters (especially the gateway) valid?
>>>
>>> --
>>> Ian.
>>>
>>>
>>>
>>> http://www.listbox.com
>>>
>>
>>
>>
>> --
>> - EJR
>>
>
>
>
> --
> - EJR
> *smartos-discuss* | Archives
> <https://www.listbox.com/member/archive/184463/=now>
> <https://www.listbox.com/member/archive/rss/184463/27398174-11508a73> |
> Modify
> <https://www.listbox.com/member/?&;>
> Your Subscription <http://www.listbox.com>
>
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
