Use wget instead of curl on OSX. That works for me.
wget --no-check-certificate https://myhost:8443/1.0
--certificate=client.crt --private-key=client.key -O - -q
{"type":"sync","status":"Success","status_code":200,"metadata":{"api_compat":1,"auth":"trusted","config":{"trust-password":true},"environment":{"backing_fs":"ext4","driver":"lxc","kernel_version":"3.16.0-37-generic","lxc_version":"1.1.0","lxd_version":"0.9"}}}
2015-05-23 20:46 GMT+02:00 <david.an...@bli.uzh.ch>:
> Hi
>
> I have the exact same problem after yesterdays update.
>
> And I suspect it is bug
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413927 or at
> least closely related.
>
> root@andel2:~# cat /proc/self/cgroup
> 10:devices:/system.slice/ssh.service
> 9:perf_event:/system.slice/ssh.service
> 8:cpuset:/system.slice/ssh.service
> 7:cpu,cpuacct:/system.slice/ssh.service
> 6:memory:/system.slice/ssh.service
> 5:freezer:/system.slice/ssh.service
> 4:net_cls,net_prio:/system.slice/ssh.service
> 3:hugetlb:/system.slice/ssh.service
> 2:blkio:/system.slice/ssh.service
> 1:name=systemd:/system.slice/ssh.service
>
> root@andel2:~# service cgmanager status
> ● cgmanager.service - Cgroup management daemon
> Loaded: loaded (/lib/systemd/system/cgmanager.service; disabled; vendor
> preset: enabled)
> Active: active (running) since Sat 2015-05-23 15:48:07 CEST; 30min ago
> Main PID: 2994 (cgmanager)
> Memory: 296.0K
> CGroup: /system.slice/cgmanager.service
> ‣ 2994 /sbin/cgmanager -m name=systemd
>
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager: Invalid path
> /run/cgmanager/fs/hugetlb/system.slice/ssh.service/lxc/s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager:per_ctrl_move_pid_main:
> Invalid path /run/cgmanager/fs/hugetlb/system.slice/ssh.servi...s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager: Invalid path
> /run/cgmanager/fs/memory/system.slice/ssh.service/lxc/s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager:per_ctrl_move_pid_main:
> Invalid path /run/cgmanager/fs/memory/system.slice/ssh.servic...s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager: Invalid path
> /run/cgmanager/fs/net_cls/system.slice/ssh.service/lxc/s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager:per_ctrl_move_pid_main:
> Invalid path /run/cgmanager/fs/net_cls/system.slice/ssh.servi...s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager: Invalid path
> /run/cgmanager/fs/perf_event/system.slice/ssh.service/lxc/s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager:per_ctrl_move_pid_main:
> Invalid path /run/cgmanager/fs/perf_event/system.slice/ssh.se...s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager: Invalid path
> /run/cgmanager/fs/none,name=systemd/system.slice/ssh.service/lxc/s0_nginx
> May 23 15:48:15 andel2 cgmanager[2994]: cgmanager:per_ctrl_move_pid_main:
> Invalid path /run/cgmanager/fs/none,name=systemd/system.slice...s0_nginx
> Hint: Some lines were ellipsized, use -l to show in full.
>
> The unprivileged containers could be stopped but trying to stop a running
> privileged container hangs and blocked the host completely.
> Even a reboot is not possible, the host answers only to ping requests, ssh
> returns with "Write failed: Broken pipe".
> And since the machine is geographically distant (and it's weekend as
> usual when such stuff happens) I cannot provide the results generated
> from the commands below.
>
> But probably I am going to run into the same error on other machines and
> will provide the results.
>
> David
>
>
> -----"lxc-users" <lxc-users-boun...@lists.linuxcontainers.org> wrote:
> -----
> To: LXC users mailing-list <lxc-users@lists.linuxcontainers.org>
> From: Serge Hallyn
> Sent by: "lxc-users"
> Date: 05/22/2015 17:44
> Subject: Re: [lxc-users] lxc-ls -f problem
>
> Quoting Dave Birch (dave.bi...@gmail.com):
> > Dave Birch <dave.birch@...> writes:
> >
> > Further update - just discovered that lxc-start now hangs for all
> > containers, even newly created ones using only the standard download
> > template on lxc-create.
> >
> > I'm pretty much dead in the water until I can work out how to resolve
> > this.
>
> Can you attach the results of
>
> sudo strace -f -ostrace.out -- lxc-ls -f
> sudo strace -f -ostrace-start.out -- lxc-start -n <container>
> sudo lxc-start -n <container> -l trace -o debug.out
>
> and show your exact steps, if you can remember them or have them in
> history, when you were originally creating these containers?
> _______________________________________________
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
> _______________________________________________
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
_______________________________________________
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
