Profile Details

Toggle Sidebar
Recent updates
  • MikeCindi
    MikeCindi replied to a discussion, ClearOS 7.3 Fully Released

    Ben Chambers wrote:

    My bad....It's not enough to have the updated clearos-base pkg if you've already installed some of the web server or flexshare packages. You needed to also run:



    B

    That seemed to fix the flexshare issue. Thank you.

    I noted on reboot (due to updated kernel today) that flexshares were not available. The folders were intact but they were empty.

    I have a couple of "custom" mounts that I add to /etc/clearos/flexshare.conf:
    storage:/mnt/storage which is physically /dev/sdb1
    backup:/mnt/backup which is physically /dev/sdc1
    When I checked mount points I noted that my root partition (/dev/sda2) was mounted on the COS generated flexshare directories (/var/flexshare/shares/backup and /var/flexshare/shares/storage)! Those two folders were empty too. This was easily fixed (umount /dev/sda2 twice although it was with some trepidation with the first one). Then all was well...so far. While I rarely need to reboot the server I would rather not have to go through this process each time. I will test whether it is truly "fixed" this weekend and report back.

  • MikeCindi
    MikeCindi replied to a discussion, ClearOS 7.3 Fully Released

    Nick Howitt wrote:
    ...
    For the first error, do you have the Web Server app installed?
    For the second, have you chosen your directory server?

    Note these are only guesses.

    The web server app is installed and running and OpenLDAP is as well.
    Ben Chambers wrote:

    @mikecindi

    For flexshare issue, make sure you have latest clearos-base:


    ...
    B

    Yep, that's what I get when i run the command.

    I find this all very odd as I have setup 7.3.0 final three times on this hardware now and each time there are different issues. I will try again and install various apps one at a time instead of several at once. Who knows maybe the fourth time is a charm... ;)

  • MikeCindi
    MikeCindi replied to a discussion, ClearOS 7.3 Fully Released

    After install, first setup, then reboot -- at the server's console I get the traditional red box for the Administrator password that is filled with "[sudo] password for clearconsole:" It does not allow any entry and typing the proper password get the same text offset down a couple of rows and over several columns on the screen. To use the console I have to open up a different one (i.e. Alt-F2). I have loaded 7.3.0 three times (for different reasons) and all have this same issue.

    Also of note is that I used the iso to create a install from USB flash but that hangs trying to get a write cache (or some such) until I get a screen full of timeout errors and drops out to a recovery console. I had to burn a DVD to be able to install.

  • DHCP server with custom MAC address list

    Hello Forum,

    I was thinking and you might know an easy sollution for me.

    In the past I was using CentOS 7 with dnsmasq and a converter located here: https://github.com/bertalanimre/dnsmasq-centos7

    Basically I had a dnsmasq.source file with the MAC addresses and IP addresses and hostnames listed. Then I used the converter which created the necesarry files for dnsmasq to work. Then I jsut restarted the service and voiala. Only the MAC addresses that I've allowed were able to connect to the DHCP server.

    In ClearOS I know I have to set the Authoritative mode off to allow only designated MAC addresses to connect but doing it on the webconfig seems slow and hard to observe for a report for example. Is there any way I can use the mentioned converter with ClearOS or just where do I have to set the MAC addresses for dnsmasq by default? I prefer doing this on the CLI if there is no more convinient way doing it on the webconfig.

    Best Regards:
    Bert

  • Installed 7.3b3 in a VM and got the following when trying to install Samba from the marketplace:

    I had similar error when trying to install 7.0 during beta testing.

  • AWStats - great webserver statistics - for both ClearOS versions

    Back many moons ago Clarkconnect, the forerunner of ClearOS, incorporated AWStats. Loved it for its webserver statistics reports. Still use it in fact. So if you want to give it a whirl, read on...

    Well, in fact, the instructions are a bit long - some 475 lines or more as it combines details for both current ClearOS versions, so am a bit reluctant to post here. Don't be put off by the length - it's relatively simple to do. Explained Step by Step The awstats rpm is installed from epel for both versions. The only 'work' is to setup some configuration files so it works under ClearOS.

    For security, access to AWStats, once installed using these instructions, is only available using https: and a userid/password pair...

    So if you are interested go to http://www.sraellis.tk/master-frame-awstats.html

    Demo here :- http://www.nltechno.com/awstats/awstats.pl?config=destailleur.fr
    AWSats Home :- http://www.awstats.org/

  • Howto - Virtualbox Headless on ClearOS

    Because ClearOS has such a small footprint it actually makes quite a good VM server for various guest OS's.

    There are threads on VMWare in the forum, and how to get that setup - so i'd thought i'd have a go with VirtualBox which also has a headerless function which can be viewed using standard Windows Remote Desktop. This makes it great for running remote OS's

    The latest version of VirtualBox is 3.1.2 however this version made some config changes from 3.0.x to the way in which storage controllers and resources are called up (long story short to enable more than one DVD drive etc)...I had more success with the tried and tested 3.0.12 method so this Howto is based around that version. Hopefully in future we'll be able to update this with the newer version. Be careful when googling for info as the syntax changed between versions.

    INSTALLATION
    First up you will need the devel tools to enable the kernel modules to be compiled during install. If you are running the PAE kernel, replace with kernel-PAE-devel


    Download the RPM for RHEL5 i386


    Installation will create a group called vboxusers, we need to add a user to this group, or create a seperate vbox specific user. I went for the latter as I wanted to keep it separate from my other accounts. User is named 'vbox' for example, we also then add the user to the vboxusers group



    VirtualBox is not LDAP aware so these need to be system user / accounts, hence the -r flag for useradd. It should create a user with an SID < 500 so that it is not removed by the system at a later date.

    This should confirm that you user has been created and associated with the group
    cat /etc/passwd | grep vbox
    cat /etc/group | grep vbox

    CREATE AND CONFIGURE A VM
    Now on to the fun bit...! Creating a VM ( I won't touch on importing your own *.vdi or *.ovf appliances here, have a read of the VirtualBox manual over here for clues http://www.virtualbox.org/manual/UserManual.html

    First switch to the new user, then we will start to create the VM. Note using the GUI is so much easier but we don't want the overheads of the full X system so stick with it :) it will start to make some sense

    Again NOTE sysntax has changed for the new 3.1.2 version, this applies to 3.0.12

    Outline steps are:- switch to vbox user (all configuration is by default stored in /home/vbox/.VirtualBox/ subfolders
    Create the VM name and register it, remember this or write it down, I called mine Windows XP


    This should return without error. The VM will be created under /home/vbox/.VirtualBox/Machines/...you can of course symlink this to another directory on the system if you wish

    Now to setup some basic parameters for the VM. We are using 512MB, boot DVD first, use basic bridged connection with the LAN interface to give it internet access. You can also specifcy --nic2 etc...or --nic1 nat. See VBoxManage man page for full config details


    Now to create the VM HD, set to 10GB, and stored under /home/vbox/.VirtualBox/HardDisks/. We then assign this HD to our VM as the primary HD device hda


    Next step to register our installation ISO with VirtualBox (this is akin to the media manager if you've used the GUI before). We then register this as the DVD drive associated with our VM. The ISO can live anywhere on your system as long as vbox can read it.


    START YOUR VM
    Thats it! a basic config that should now get a VM install running. To start our VM headerless we now run the following, and then connect remotely using Windows Remote Desktop to ClearOS (port 3389 is used by default). Note the & at the end, this will force it to run in the background, so you should ensure you shutdown the VM correctly or use VBoxManage to control / save the states on exit)


    To detach the DVD iso (i.e. eject it) use the following

    You may also try - if the VM is running


    GUEST ADDITIONS
    Now I found that the display and mouse did not correlate very well until I install the guest additions. So....register and attach the guest additons ISO, then boot your VM and run the installer from within the OS


    Enjoy! :)
    For more configuration options refer to http://www.virtualbox.org/manual/UserManual.html#vboxmanage-modifyvm Particularly for increasing the video card memory size, NIC options etc.

    TIPS - To be completed....
    Want to see a VM config? use VBoxManage showvminfo "WindowsXP"
    Want to see HD config? use VBoxManage showhdinfo harddiskname.vdi
    Want to change Video RAM allocated to VM? use VBoxManage modifyvm "WindowsXP" --vram 128MB
    Want to enable USB and USB2.0? use VBoxManage modifyvm "WindowsXP" --usb on --usbehci on
    Want to shutdown a VM? use VBoxManage controlvm "WindowsXP" acpipowerbutton (for instant off, use poweroff)
    Need to press CTRL-ALT-DEL to login over RDP? it's locked solely to the local machine, so use CTRL-ALT-END instead ;)
    Want to see other ostypes? use VBoxManage list ostypes

  • Because ClearOS has such a small footprint it actually makes quite a good VM server for various guest OS's.

    There are threads on VMWare in the forum, and how to get that setup - so i'd thought i'd have a go with VirtualBox which also has a headerless function which can be viewed using standard Windows Remote Desktop. This makes it great for running remote OS's

    The latest version of VirtualBox is 3.1.2 however this version made some config changes from 3.0.x to the way in which storage controllers and resources are called up (long story short to enable more than one DVD drive etc)...I had more success with the tried and tested 3.0.12 method so this Howto is based around that version. Hopefully in future we'll be able to update this with the newer version. Be careful when googling for info as the syntax changed between versions.

    INSTALLATION
    First up you will need the devel tools to enable the kernel modules to be compiled during install. If you are running the PAE kernel, replace with kernel-PAE-devel


    Download the RPM for RHEL5 i386


    Installation will create a group called vboxusers, we need to add a user to this group, or create a seperate vbox specific user. I went for the latter as I wanted to keep it separate from my other accounts. User is named 'vbox' for example, we also then add the user to the vboxusers group



    VirtualBox is not LDAP aware so these need to be system user / accounts, hence the -r flag for useradd. It should create a user with an SID < 500 so that it is not removed by the system at a later date.

    This should confirm that you user has been created and associated with the group
    cat /etc/passwd | grep vbox
    cat /etc/group | grep vbox

    CREATE AND CONFIGURE A VM
    Now on to the fun bit...! Creating a VM ( I won't touch on importing your own *.vdi or *.ovf appliances here, have a read of the VirtualBox manual over here for clues http://www.virtualbox.org/manual/UserManual.html

    First switch to the new user, then we will start to create the VM. Note using the GUI is so much easier but we don't want the overheads of the full X system so stick with it :) it will start to make some sense

    Again NOTE sysntax has changed for the new 3.1.2 version, this applies to 3.0.12

    Outline steps are:- switch to vbox user (all configuration is by default stored in /home/vbox/.VirtualBox/ subfolders
    Create the VM name and register it, remember this or write it down, I called mine Windows XP


    This should return without error. The VM will be created under /home/vbox/.VirtualBox/Machines/...you can of course symlink this to another directory on the system if you wish

    Now to setup some basic parameters for the VM. We are using 512MB, boot DVD first, use basic bridged connection with the LAN interface to give it internet access. You can also specifcy --nic2 etc...or --nic1 nat. See VBoxManage man page for full config details


    Now to create the VM HD, set to 10GB, and stored under /home/vbox/.VirtualBox/HardDisks/. We then assign this HD to our VM as the primary HD device hda


    Next step to register our installation ISO with VirtualBox (this is akin to the media manager if you've used the GUI before). We then register this as the DVD drive associated with our VM. The ISO can live anywhere on your system as long as vbox can read it.


    START YOUR VM
    Thats it! a basic config that should now get a VM install running. To start our VM headerless we now run the following, and then connect remotely using Windows Remote Desktop to ClearOS (port 3389 is used by default). Note the & at the end, this will force it to run in the background, so you should ensure you shutdown the VM correctly or use VBoxManage to control / save the states on exit)


    To detach the DVD iso (i.e. eject it) use the following

    You may also try - if the VM is running


    GUEST ADDITIONS
    Now I found that the display and mouse did not correlate very well until I install the guest additions. So....register and attach the guest additons ISO, then boot your VM and run the installer from within the OS


    Enjoy! :)
    For more configuration options refer to http://www.virtualbox.org/manual/UserManual.html#vboxmanage-modifyvm Particularly for increasing the video card memory size, NIC options etc.

    TIPS - To be completed....
    Want to see a VM config? use VBoxManage showvminfo "WindowsXP"
    Want to see HD config? use VBoxManage showhdinfo harddiskname.vdi
    Want to change Video RAM allocated to VM? use VBoxManage modifyvm "WindowsXP" --vram 128MB
    Want to enable USB and USB2.0? use VBoxManage modifyvm "WindowsXP" --usb on --usbehci on
    Want to shutdown a VM? use VBoxManage controlvm "WindowsXP" acpipowerbutton (for instant off, use poweroff)
    Need to press CTRL-ALT-DEL to login over RDP? it's locked solely to the local machine, so use CTRL-ALT-END instead ;)
    Want to see other ostypes? use VBoxManage list ostypes

  • MikeCindi

    If you solve your other KDE problem this one will probably go away.

    FWIW "yum groupinstall "Development Tools" does not work post ClearOS5.x. For installing the development environment please see this link, but don't bother with installing an editor unless you need it.

  • Thanks, Nick.

    Still curious if Matthew had any success.