|
|
| Subject: | Zenoss core 5 cli access |
| Author: | [Not Specified] |
| Posted: | 2015-03-11 12:04 |
I wanted to get to the cli for the zenoss instance so I can run some scripts that do things such as rename devices with their title as well as using zenbatchload to load all my devices.
I tried
serviced service attach Zenoss.core
but I get prompted authentication no matter what account I use.
my user is part of the docker group, and I have tried this with root and serviceman accounts also.
Any ideas
I'm running this on CentOS 7x64, I used the autodeploy script to set everything, and I have active devices in the instance and everything else seems to be functioning normally.
| Subject: | Is Zenoss.core service |
| Author: | Jan Garaj |
| Posted: | 2015-03-11 12:43 |
Is Zenoss.core service/container running (DSTATE=1)
[root@localhost ~]# id
uid=0(root) gid=0(root) groups=0(root)
[root@localhost ~]# serviced service list
NAME SERVICEID INST IMAGEID POOL DSTATE LAUNCH DEPID
Zenoss.core bpw6rp3dlv2zy7d5ugd4f1bqj 1 .../bpw6rp3.../core_5.0 default 1 auto zenoss
RabbitMQ 2n7rk4bo0ql9hkxavlzjzq1tt 4 .../bpw6rp3.../core_5.0 default 1 auto zenoss
zenjobs 38un0dt7p29c5vtffp2h1f7hq 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
MetricShipper 5r88aul2rdp00ufjvfth4dbw6 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
redis 6445wrz03pkz6qfahdhelo650 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zeneventd 69oldu9kohwph2wsf9qq1ntnb 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
localhost 6w8t4oc3sv2rkkh35xoe0u81t 0 default 0 auto zenoss
zenhub 6eb7mjb4obdwxu64xeeq38dqc 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
localhost asrddvav4fe564mi1hr0hrb13 0 default 0 auto zenoss
zentrap 53n2cretsua44hzo9hvxf3oir 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zenstatus 59ghfd9x965d85wui1gjmylmy 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
MetricShipper 5dgemczvuydyg3jv70gce9y4a 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
collectorredis 5osx0eygh8ookq76b5rih7n9x 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zenperfsnmp 5t5xpptdzvmghffai9ji6uei9 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zenmodeler 6p6e53a7jfx3oc6ux86h7y94 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zminion 7ww9pvnmx35b7jd02rbak301b 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zenping 80d9xofueypufx2qe1hjrfnw8 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zensyslog aph7wglseyajipvvj602zncb 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zenjmx b90maydlabbww987t3ucj7d1o 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zencommand e2halc37kvtyrmop6kkj2egu7 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zenprocess e8vmfflpjh8aj1ixun0gg80wt 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zenpython ln4d7b78b0d72m7ft5fwqhdg 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
Zope 94o4pk3ccnvf0pkrsncckjwt8 1 .../bpw6rp3.../core_5.0 default 1 auto zenoss
zenactiond 9lfyy3moxp4a9uo4bi87dieee 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
opentsdb 9r511b2h3159bn4gugkb2k51l 1 .../bpw6rp3.../opentsdb default 0 auto zenoss
CentralQuery 9wu3xs2su9m08a3zz6xhgylxp 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
HBase cufos81a2p9t8c0g2vhnt2w24 0 default 0 auto zenoss
HMaster 17e16yacifkxab4i2886g3eh1 1 .../bpw6rp3.../hbase default 0 auto zenoss
RegionServer 3macbi737jx6tpq9ile67lulu 1 .../bpw6rp3.../hbase default 0 auto zenoss
ZooKeeper 9j3w4mc8l17svx97vpeidwast 1 .../bpw6rp3.../hbase default 0 auto zenoss
MetricConsumer cvhyqoei3jrgnehxdwmddv7io 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
MariaDB d60mi8cxbzgbnoewdfbbhd8cu 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
zeneventserver dqmjz13br752hh4jnnnm6qxfz 1 .../bpw6rp3.../core_5.0 default 0 auto zenoss
[root@localhost ~]# serviced service attach Zenoss.core
[root@ffde257fc525 /]# ls
bin dev etc home lib lib64 lost+found media mnt opt proc root run sbin selinux serviced srv sys tmp usr var
[root@ffde257fc525 /]# exit
exit
[root@localhost ~]#
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | [root@monitoring ~]# id |
| Author: | Jan Garaj |
| Posted: | 2015-03-11 17:18 |
[root@monitoring ~]# id
uid=0(root) gid=0(root) groups=0(root) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 => SELINUX
Could you show your /etc/selinux/config please
If selinux is disabled, try to reboot machine.
Reboot is part of the install guide, but reboot is not required in my script. Let me know if it's ok after reboot.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | I have never tried to attach |
| Author: | Matt |
| Posted: | 2015-03-20 19:50 |
I have never tried to attach to the Zenoss.core instance directly...
However I believe that his is also not recommended and might be the reason why you're having trouble doing so!
If you want to interact with zenoss, then I would attach to zope, e.g. serviced service attach zope su - zenoss -l
Let me know if that works.
| < |
Previous Import data from Zenoss 4.2.5 |
Next Zenoss 5.0 -> how to change the ip address of the master host |
> |