I was right the first time. You need to use `mysqld`. [vagrant@node1 ~]$ service mysqld status mysqld status unknown due to insufficient privileges.
[vagrant@node1 ~]$ sudo su - [root@node1 ~]# service mysqld status mysqld (pid 1734) is running... On Tue, Oct 11, 2016 at 10:20 PM, Nick Allen <[email protected]> wrote: > Try with "mysql" instead of "mysqld". I am probably remembering the > service name incorrectly. > > On Oct 11, 2016 9:59 PM, "Rita McKissick" <[email protected]> > wrote: > >> Hi Nick, >> >> Aah, I had forgotten about this. Can you tell where I run "service mysqld >> status" and "service mysqld >> start” from. I keep getting mysqld: unrecognized service and I’m pretty >> sure I’m running the command from the wrong location. >> >> Thanks, >> >> Rita >> >> Rita McKissick ! Sr. Technical Writer >> >> >> >> >> >> >> >> >> On 10/11/16, 4:11 PM, "Nick Allen" <[email protected]> wrote: >> >> >To your second point about no data showing up, I have noticed that MySQL >> is >> >sometimes not started which prevents the enrichment topic from moving >> >data. >> > >> >I have not investigated but it might be due to memory constraints on the >> >virtual node. >> > >> >Check if MySQL is running with "service mysqld status" and "service >> mysqld >> >start". You may need to redeploy the topology after that restart if you >> >don't want to wait a while for things to heal on their own. >> > >> >On Oct 11, 2016 6:35 PM, "Rita McKissick" <[email protected]> >> >wrote: >> > >> >> *** Resending because this message seemed to disappear into the ether >> and >> >> I didn’t receive a copy of it. >> >> >> >> I’m having difficulties with the latest Quick Development Platform >> >> installation. During deployment I received the following error message: >> >> >> >> ------------------------------ >> >> >> >> TASK [metron_common : Check for Metron jar path] >> >> ******************************* >> >> fatal: [node1 -> localhost]: FAILED! => {"changed": false, "failed": >> true, >> >> "module_stderr": "sudo: a password is required\n", "module_stdout": "", >> >> "msg": "MODULE FAILURE", "parsed": false} >> >> >> >> PLAY RECAP ****************************** >> ****************************** >> >> ********* >> >> node1 : ok=20 changed=2 unreachable=0 >> failed=1 >> >> >> >> Ansible failed to complete successfully. Any error output should be >> >> visible above. Please fix these errors and try again. >> >> >> >> --------------------------------- >> >> >> >> >> >> Everything up to this point looked fine. >> >> >> >> By the way, I installed the latest Quick-Dev installation earlier this >> >> afternoon and it didn’t install/configure any topologies. That’s why I >> did >> >> a second install … which turned out even worse. >> >> >> >> Anyone else having this issue? Can someone help me with a fix or >> >> workaround? >> >> >> >> Thank you! >> >> >> >> Rita >> >> >> >> Rita McKissick ! Sr. Technical Writer >> >> >> >> >> >> >> > -- Nick Allen <[email protected]>
