Thanks guys for your help on Thanksgiving night!
William Ratcliffe -
The 20151112T052215Z release that you upgraded to is what I'm already
running. I see now, however, that a new release was released on
Thanksgiving: 20151126T062747Z. Later tonight I'll connect to my management
VPN and start the upgrade.
Cody Mello -
Thanks for the cool dtrace command! This is the first time that I've ever
run anything like that. Definitley cool technology. Here is what I got:
By the time the vmadm create command returned with this:
[root@00-25-90-b5-25-a8 /opt/json]# vmadm create -f lxtest.json
timed out waiting for /var/svc/provisioning to move for
3007419e-a40e-4083-a26d-b19aebd0a9a8
The dtrace command had printed all of this:
[root@00-25-90-b5-25-a8 /opt/json]# 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); }'
dtrace: description 'proc:::exec-success ' matched 1 probe
dtrace: description 'fbt:genunix:exit:entry ' matched 1 probe
CPU ID FUNCTION:NAME
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 22192 exit:entry zoneadmd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 7982 exec_common:exec-success lxinit execed in
3007419e-a40e-4083-a26d-b19aebd0a9a8
5 7982 exec_common:exec-success ipmgmtd execed in
3007419e-a40e-4083-a26d-b19aebd0a9a8
5 22192 exit:entry ipmgmtd exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
6 22192 exit:entry metadata exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
4 7982 exec_common:exec-success routeinfo execed in
3007419e-a40e-4083-a26d-b19aebd0a9a8
4 22192 exit:entry routeinfo exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
3 7982 exec_common:exec-success init execed in
3007419e-a40e-4083-a26d-b19aebd0a9a8
4 22192 exit:entry ipmgmtd exited with 9 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
6 22192 exit:entry init exited with 9 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
1 22192 exit:entry zsched exited with 0 in
3007419e-a40e-4083-a26d-b19aebd0a9a8
In the zone, there appears to be issues affecting the second time ipmgmtd
runs, after it gets called by init. If I can locate it, then perhaps I can
determine the problem after inspecting how ipmgmtd is being run.
On Fri, Nov 27, 2015 at 3:36 AM, William Ratcliffe <[email protected]>
wrote:
> Evan,
>
> I had exactly the same problem with the same image this week. What version
> of smartos are you running?
>
> I was running a version of smartos from Jan2015; I updated to
> joyent_20151112T052215Z and it worked straight away
> on reboot.
>
> My json looked like this
>
> {
> "brand": "lx",
> "image_uuid": "52be84d0-6b06-11e5-a4c0-9f0c52fa368a",
> "alias": "ubuntu-1404-lxzone",
> "kernel_version": "3.13.0",
> "hostname": "ubunut-1404-lx-zone",
> "max_physical_memory": 4096,
> "quota": 40,
> "resolvers": ["8.8.8.8", "208.67.220.220"],
> "nics": [
> {
> "nic_tag": "admin",
> "ip": "192.168.1.83",
> "netmask": "255.255.255.0",
> "gateway": "192.168.1.1"
> }
> ]
> }
>
> Regards
> Will
>
> On 26/11/2015 21:16, 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
> }
> ]
> }
>
> Proceeded to create the zone via:
>
> # vmadm create -f lxtest.json
>
> After a while, this is what was output to the terminal:
>
> timed out waiting for /var/svc/provisioning to move for
> 3168e569-3687-4367-abba-1a35094e3d33
>
>
> I can see that the vmadm command has failed:
>
> # vmadm list
> UUID TYPE RAM STATE
> ALIAS
> 3168e569-3687-4367-abba-1a35094e3d33 LX 2048 failed
> lxtest
>
>
> I'm running release version 20151112T052215Z.
>
>
> --
> - EJR
>
>
> *smartos-discuss* | Archives
> <https://www.listbox.com/member/archive/184463/=now>
> <https://www.listbox.com/member/archive/rss/184463/24484565-d47e1b4e> |
> Modify
> <https://www.listbox.com/member/?&;>
> Your Subscription <http://www.listbox.com>
>
--
- EJR
-------------------------------------------
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
