These are two separate messages.
Code: Select all
/etc/cron.daily/logrotate:
[Sun Apr 12 06:25:17 2015] [warn] The Alias directive in /etc/phpmyadmin/apache.conf at line 3 will probably never match because it overlaps an earlier Alias.
This message seems to tell you nearly everything you need to know. It's a warning ([warn]), so no, this issue shouldn't cause any serious harm. You already figured out that you should check line 3 of that phpmyadmin config file. It's basically saying that an Alias directive declared before the Alias directive mentioned ("Alias /phpmyadmin /usr/share/phpmyadmin") in /etc/phpmyadmin/apache.conf is too similar and therefore the Alias directive in /etc/phpmyadmin/apache.conf may never be applied to any requests because the prior Alias will catch any requests that might have matched "/phpmyadmin".
In order to find the earlier Alias directive this warning is describing, you can check through the other apache2 config files. Check /etc/apache2/apache2.conf as this file will usually tell you the locations of all of the other config files you might want to check in your search for the other overlapping Alias directive. You'll probably want to check for any files in these directories: /etc/apache2/conf.d/*, /etc/apache2/mods-enabled/*, /etc/apache2/sites-enabled/*. Those last two locations are directories that normally only contain symlinks pointing to config files which are actually located in /etc/apache2/mods-available/* and /etc/apache2/sites-available/*. Seeing which symlink files are located in the *-enabled directories can be helpful for letting you know which config files are currently enabled and being used in the related *-available directories. You should view/edit the config files in the *-available directories. See if you can find another apache2 config file which contains an Alias directive similar to the "/phpmyadmin" Alias.
Code: Select all
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
You're seeing this message because you aren't using a domain name. This should be expected for most users playing around with non-public installations of the apache2 web server on a Raspberry Pi.