This is the most insecure thing you can do to your linux system. That said however, when working on development systems at home I like to logon as SSH. Granted this is behind a firewall to a linux system with no access from the internet.
This was tested on Ubuntu 14.x on a Raspberry Pi.
I do this out of laziness. NEVER do this to an internet accessible system.
Continue reading “Allow Root to SSH for Ubuntu”
This works for Linux and Mac command lines. It’s fast and easy to remember. Ready?
That’s it. It just returns your external IP. If you have curl under Windows it should work there too.
After making an image of a physical linux box (Dell hardware running CentOS), I converted the IMG file to a VDH file and after booting had many issue. One of which was the following error which caused all databases on the respective volume to fail because the volume was in read-only mode.
EXT3-fs error (device hda3) in start_transaction: Journal has aborted
Turns out, the system is telling me that it’s detected a file system/journal mismatch, and it can’t utilize the journal any longer. When this situation pops up, the file system gets mounted read-only. To fix the situation, I had to boot the system (now in the VM environment) in single user mode, dismount the volume and fix it.
I first started by removing the journal from the file system:
# tune2fs -O ^has_journal /dev/hda3
Then I tried to fsck it to correct any possible problems:
# e2fsck -p -f -v /dev/hda3
Unfortunately this lead me to another error: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options).
Ugh. fsck again….I had originally run it without the -f option and it found no errors, yet it refused to mount in read-write mode. So now running it sans the -p option, -f forcing it to check it anyway, seems to have helped- but this time I needed to be present to hit y to every single error. There were hundreds.
Once that finished I ran it again with the -y option to see if it picked up anything and it was clean!
Time to make a new journal which makes the partition an ext3 file system again:
I can now mount the partition as an ext3 partition:
# mount -t ext3 /dev/hda3 /mnt/fixed
After rebooting the system seems happy once again with no mounting errors. Quick and simple!
I use several QNAP devices from the large 24 drive down to a personal 2 drive. I’ve found that they are pretty good and you can do a lot with them as they’re basically Linux boxes with a pretty web interface.
Here are some useful console commands for restarting specific services.
First, to restart basically everything you can issue this command:
One of the most common ones is to restart smb:
Here’s a list of other common ones: (They’re all in /etc/init.d)
I believe they will all accept the restart option. They will accept start/stop options.
Setting up SNMP (Simple Network Management Protocol) on a CentOS machine is a very quick and easy process and I often forget so here’s a quickie on how.
Install the SNMP daemon by running the following command:
yum install net-snmp
Once SNMP is installed you want to install the configuration utility. I always forget this. It makes it easy to configure SNMP for both the community string, SNMP version and basic security.
yum install net-snmp-utils
Once the configuration tool is installed, run it:
snmpconf -g basic_setup
As you run through the configuration utility it will present you with many options. Depending on how you have your remote monitoring setup (Cacti/Nagios) you will need to choose the options that work for you.
Once done, you will need to copy the configuration file to the correct directory. In most cases it will need to be moved from “/root/snmpd.conf” to “/etc/snmp/snmpd.conf” – You will need to overwrite the existing conf file in the /etc/snmp/ directory.
mv /root/snmpd.conf /etc/snmp/
Once the configuration file has been moved over you can restart SNMP.
service snmpd restart
The last thing you need to do is have SNMP start at boot time. If you do not run the following command you will need to manually start SNMP after a reboot.
chkconfig snmpd on
At this point you should be set. If for some reason you are running the firewall will need to open port 161 for UDP & TCP traffic to allow SNMP to be accessed remotely.
I don’t know why I didn’t have notes on this already. I’ve done it dozens of times. So here’s the write up.
I use Ubuntu and it uses the syslog facility/daemon called rsyslogd. Its configuration file is located here:
This file tells the deamon where to log each type of message. For example the follow entry means that all cron message are sent to /var/log/cron.log:
Continue reading “Sending Syslog logs from Ubuntu to a remote syslog server”
I just had the need to truncate all the tables in of my databases. Basically I wanted the data gone but the schema to stay. Below is the linux shell command I used to truncate the tables.
I’ve also included how to straight up drop the tables too- just keep in mind dropping tables dumps the schema and data.
mysql -Nse 'show tables' DATABASE_NAME | while read table; do mysql -e "truncate table $table" DATABASE_NAME; done
mysql -Nse 'show tables' DATABASE_NAME | while read table; do mysql -e "drop table $table" DATABASE_NAME; done
Make sure the user executing this has privileges to the database in question.