I have a RedHat server that is getting full on /dev/mapper/rhel-root but I am not adding files to the server.
How can I know the one eating the space?
Related
Logarchmeth and failarchpath configured to different local disk paths and I made the Logarchmeth path unavailable (removing the privileges)
Failarchpath path was still not used at any point (all the logs were kept in the log path), but the database was up and running for the whole time
Once the Logarchmeth path got available again, the backup restarted.
Don't understand why logs were not backed up to the location pointed to by failarchmeth setting.
I'm trying to build an image using bitbake for the i.MX8 board.
I'm following these instructions:
https://www.nxp.com/docs/en/user-guide/IMX_YOCTO_PROJECT_USERS_GUIDE.pdf
Since I do not have enough space in local HDD, I'm using an external USB HDD (I have other unrelated stuff stored in this HDD).
I have been successfull at executing the imx-setup-release.sh script in that document, with which I built a configuration for the imx8mm-lppddr4-evk machine using the fslc-wayland distro.
However, when I try a command, such as "bitbake core-image-minimal", I get several failed tasks. It seems that the common deminator is the fact that, for some reason, when the path to my build folder is passed (which is within the external HDD), it is considered an invalid argument.
I get messages such as this:
OSError: [Errno 22] Invalid argument: '/media/home_dir/427AD2297AD2198D/imx-yocto-bsp/build_fslc_wayland_imx8mm_lpddr_evk/sstate-cache/95/51/sigtask.1jbsd4s4' -> '/media/home_dir/427AD2297AD2198D/imx-yocto-bsp/build_fslc_wayland_imx8mm_lpddr_evk/sstate-cache/95/51/sstate:core-image-minimal:imx8mm_lpddr4_evk-fslc-linux:1.0:r0:imx8mm_lpddr4_evk:3:955169ece771b852dc433575442e7ed805ac56cbcb1ebd3aa913a632da23a46b_clean.tgz.siginfo'.
It seems that bitbake is having trouble parsing the path to my HDD (that 427AD.../ folder).
What should I do to fix this?
The issue was that my HDD was not formatted with an ext4 format. Once I did that, those errors went away.
I am trying to follow the instructions on https://kafka.apache.org/quickstart to try and start a Kafka install and then send some messages from a scala client.
I am using a windows system.
I am getting this error(see screencap) when i run the zookeeper instance.
The reason most probably is because your directory path has a space - “Development Tools”. Try running this in a path which has no spaces. I guess the space is causing some path issues in the shell script.
Also, I assume that you downloaded the binary and not the source files?
Hope it works and let us know.
I've had Nginx & Thin playing nicely on Ubuntu 10.04 for a couple of years. I have a script in /etc/init.d that starts Thin, using some .yml files in /etc/thin.
All of a sudden restarting Thin for any reason causes a permission denied error in Nginx.
Thin is running on a couple of sockets in /tmp, owned by root. I don't know if that was always the case...but if I change the owner of the socket to www-data (used by Nginx) everything works fine. So I wrote another script to handle it.
Thin is running v1.2.7, and Nginx is 0.7.65. Neither has changed. I did upgrade to Ruby 1.9.3p194 from 1.9.2p290.
Does anybody else have this issue, and have you found a more reasonable fix than "manually" updating permissions?
Upgrading Thin to 1.3.1 solved it. I should've tried that right away, but I had issues with a staging server.
Anyway. Maybe this will help someone else.
CentOS 5.5
I have a web application running on a server and it needs access to another CentOS server's file system running in the same network (via private IP). After doing a bunch of googling it looks like mounting the drive via NFS is a good way to go, but I'm not finding any good step by step instructions on how to go about it. I've read the man docs on the mount command and read some docs on the CentOS wiki as well but I feel like I'm missing something. Here is what I'm trying
mount -t nfs my.ip.address:/somePath /somePath/mount
I keep getting a 'no route to host' error but I can ping the server just fine. I'm guessing that I am possibly missing a port I need to open or something, but again, can't find information that makes sense to a non-sysadmin like myself.
Thanks for any help.
I ran across this, followed it step by step, and now I'm up and running!
http://www.cyberciti.biz/faq/centos-fedora-rhel-nfs-v4-configuration/