I can't even get started on Pset7 because killall isn't stopping the pset6 server - which is working just fine, can I say. When I run "killall -9 server" from ~/workspace/pset7/public/ I get the response: server: no process found but when I open my public directory Pset 6 comes up and that cat still appears when I click on cat.html
First of all, congratulations on finishing
ps -awux | grep server to see if there is a server process running. If there is, it will return a line that starts with the process number. Let's say that the process number turns out to be 42. Then you can kill the process with
kill -9 42.
~/workspace/ $ ps -awux |grep server [The first line will be very long and contain personally identifying information, so I snipped it here] ubuntu 1785 0.0 0.0 7448 884 pts/1 S+ 11:02 0:00 ./server public/ ubuntu 2018 0.0 0.0 10556 1568 pts/3 S+ 11:02 0:00 grep --color=auto server
In this example, the process number is 1785, so the command will be:
kill -9 1785
Another possibility is that the zombie server process which needs to be killed is really an
apache2 process. If this is the case,
killall -9 apache2 may be helpful.
EDIT: I always neglect to mention (and @DinoCoderSaurus never fails to remind me!) that this problem is most often caused because you are viewing an old version of this URL which is stuck in your browser's cache. If that's the case, Ctrl-F5 will bypass the cached version and reload the resource via HTTPS.
EDIT2: as for your problem with phpMyAdmin, the best advice I can offer is here.