Beiträge von johny_sketo

  • Temperature Sensor

    Zitat von "logan_fre"


    Thanks for this. I tried that but it didn't make any difference. After trying different things, I found that it was because there was a TAB before the EOF. Now I don't get an error, but there are no graphs. I'm not sure it is worth it to keep fooling around with it. I noticed that under the S.M.A.R.T section you can see the drive temps so that will probably be enough for me.


    Can you check what do you see inside the following folder

    Code
    /var/lib/collectd/rrd/localhost


    What mainboard do you use?

  • Temperature Sensor

    [quote="logan_fre"]Hello. I was trying to setup temperature monitoring using the first post here but I get this error:


    Code
    /usr/share/openmediavault/scripts/collectd.d/sensors: line 70: warning: here-document at line 11 delimited by end-of-file (wanted `EOF')


    Check if you have any Space after the last EOF.

  • Changes in plugins with openmediavault 0.3.0.23

    Zitat

    To use triggers you simply have to create the file debian/xxxx.triggers which contains (until now) the following content:


    Code: Select all
    activate update-locale
    activate update-fileperms


    Sorry for my stupid question but is it possible to give me some instruction how I can do this?Thank you in advanced

  • owncloud

    Zitat von "iKai"

    How can i change the file directory? I will show the files from my root share like the UUID.


    To be honest I do not know how. I know that it uses the data folder inside the owncloud folder to built the data/users structure, but I cannot find anywhere an option to change this folder.

  • owncloud

    Zitat von "trza"

    What is WINSCP?


    WinSCP is a windows program that uses SSH protocol to transfer files, at least that is the reason I use it for. It looks very much like Windows Explorer and it is very easy to use.


    Zitat von "trza"

    I think "SOMETHING STRANGE" is referred to as the UUID? Seems like each physical drive gets something akin to a Serial Number to identify it. The number is so long it makes things seem impractical to use a command line to reference it.


    Yes, I refer to the UUID. I know it is a little bit difficult but we are using it for only a few times and you can copy/paste the whole SN.


    Zitat von "trza"


    Here, it seems like you're creating a User named "ocuser", adding them to the "adm" and "users" groups. If your account is a member of either group, you can see the "owncloud" share. So if somebody wanted any user to be able to access /owncloud, they could just give permission to the "users" group?


    I create a new user because I cannot add my account, or anybody already configured at OMV, at the Allow PHP Script part of Website plugin. I am sure that the group part may be wrong but as I said I am not expert and I wrote just what made my system work (OMV, OC with Webdav)


    Zitat von "trza"

    I think all of this gives anybody on your network access to "/owncloud". If this is the case, you wouldn't need to make a user?


    Again, the new user is necessary. The permissions may be wrong, please somebody corrects them in order to have maximum security

  • owncloud

    Zitat von "stonerhawk"


    After launching owncloud i didn't notice any setup wizard.
    Where i can find and manage owncloud database?


    Dear stonerhawk,


    The first time you open the OC webgui you should see the login page, but with some differences. The first time it lets you create a user and setup the DB part. In our case and since we use MySQL you should see the fields I wrote. If you have others DBs it will let you choose which one you wish to use. Also, have in mind that all these appear after you choose Allow PHP Script at the Website plugin.

  • owncloud

    Again I am not an Linux/Unix expert, I have just create a step by step guide to the steps I made in order to make everything work (OMV and Owncloud), As you will see below for some steps I am not 100% sure. Many steps comes from the old forum and other people wrote these first. As advise, first try it at a VirtualBox setup to be sure and then at your server. I am not responsible if this create any issue at your server. I hope someone who knows more than me corrects any mistakes I made.


    OK..lets start. All packages version may change so keep that in mind in order to change the code...


    From a brand new installation first of all we have to install the omvpluginorg from

    Code
    http://packages.omv-plugins.org/pool/main/o/openmediavault-omvpluginsorg/openmediavault-omvpluginsorg_0.3.2~3.gbpa0b737_all.deb

    . Upload it to the server by the OMV GUI, at System / Plugins. Install it. Refresh OMV page nad press Check in order to refresh the plugins list.
    Chooce openmediavault-website 0.3.4, install it
    Choose openmediavault-mysql 0.3.4.2, install it
    Refresh the OMV page and choose the MySQL plugin in order to set a root password. (I am not 100% sure if this is mandatory, but just to be sure)
    At NEW PASSWORD set your password and CONFIRM IT, press OK.


    Go to Share Folders, press ADD and put the following
    Name : owncloud
    Volume: choose your disk
    Path:owncloud


    SSH to your server or by keyboard


    Code
    apt-get install php5-gd


    press Y when asks.

    Code
    wget http://owncloud.org/release/owncloud-4.0.6.tar.bz2

    then

    Code
    tar -xjf owncloud-4.0.6.tar.bz2

    (#WHEN I TRIED THE LAST TIME THIS COMMAND FAILED, I DO NOT KNOW WHY, AND I HAD TO UNTAR IT BY WINSCP AND WINRAR)


    Log in through WINSCP. Copy all the files and folders coming from this tar.bz2 file and paste them inside the owncloud folder we created before, in my installation it was

    Code
    /media/SOMETHING STRANGE/owncloud

    , then

    Code
    chown -R www-data:www-data /media/SOMETHING STRANGE/owncloud


    Go back to the OMV GUI, at Users, click Add, name ocuser, group adm and users (I am not 100% sure if this is correct but it works)


    Go at the Website plugin, tick ENABLE, go to Document Root and choose owncloud [on/dev/sdb1] (THIS MAY BE DIFFERENT)
    Virtual host type:Port Based
    Virtual Host Port:8181
    Go to the PHP section and Tick Allow PHP Script
    User: ocuser
    Go to the Options section, tick Indexes
    Go to Allow Override and tick next to all
    Click OK (I got a error message but it says it is a communication failure so ignore it)


    Go to the Shared folders again, choose owncloud and press ACL
    Change the permissions as follows
    owncloud-> ocuser READ/WRITE and at the extra options Others Read/Write
    expand owncloud
    apps->ocuser READ/WRITE
    config->ocuser READ/WRITE


    edit the file

    Code
    /etc/apache2/sites-enabled/zzz-omv-website-vhost


    Mine looks like this

    THE DIRECTORIES WILL NEED CHANGE SINCE IT IS TAKEN FROM MY SETUP, SO CHANGE IT. ALL THE OTHERS NEED TO BE LIKE THIS IN ORDER TO MAKE THE OWNCLOUD GUI WORK TOGETHER WITH THE WEBDAV FEATURE {THIS TOOK ME 2 WEEKS TO MAKE IT WORK, SINCE THE ERROR WAS A MISSING "+" AT Options +ExecCGI :twisted: :twisted: :twisted: }
    Go back to SSH or keyboard of the server

    Code
    a2enmod rewrite

    and

    Code
    a2enmod headers

    , then restart the apache server by

    Code
    service apache2 restart


    Now you can log in at the Owncloud Webgui by

    Code
    http://SERVERIP:8181

    we will see the setup page, enter USER, PASSWORD , at MySQL DB use USER:root, Pass:the password you set before at the MySQL plugin, BD name : owncloud, localhost and then press Complete


    At this step you will not be able to login at the OMV webgui page, you will get an error. Use WinSCP. locate php.ini in the

    Code
    /var/www/omv-website-vhost/

    find the

    Code
    session.save_path

    , remove the

    Code
    ;

    in front and edit as

    Code
    session.save_path=("/tmp")

    (NOT 100% SURE)


    Then find the php.ini in

    Code
    /var/www/openmediavault/cgi/

    find the

    Code
    session.name

    and change it to something (?), mine is session.name=("OMVSESSION") (NOT 100% SURE)


    Now you can log in to the OMV Gui again :D:D:D


    Finally to get Owncloug to work propertly edit the following

    Code
    /var/www/omv-website-vhost/php.ini

    and add

    Code
    max_execution_time=3600
max_input_time=3600
memory_limit=512M
post_max_size=2000M
upload_max_filesize=2000M
max_file_uploads=10

    at the end.
    Also edit

    Code
    /etc/apache2/httpd.conf

    and add

    Code
    <ifmodule mod_fcgid.c>
MaxRequestLen 20000000000
</ifmodule>

    With these changes, and after a restart you will be able to upload files up to 2GB size each.


    I hope these helps :D

  • owncloud

    I will try to make one step by step guide. Sorry for being late but I had some issues that could not wait :(
    Once again I am not Linux/Unix expert. I am not 100% sure that these steps will work at your system and everything I write I have tested at my system (i386) and found it at the old forum and the OC forum.
    Be patient for a little while :)

  • owncloud

    It is possible to implement Owncloud at OMV. There are some issues but you can overpass them and finally install it succesfully. First of all you need Website plugin and Mysql also. If you search the old forum you can find the how to install it and overpass the problems. I have install it (following these info) and I will try to create a How to with all the required configurations you need.

  • Temperature Sensor

    First of all, I am not a Linux/Unix expert, I am just noob at these :)
    I believe that the OMV does not shut down your system. I do not believe there is such an option at the GUI. I believe the shutdown temperature is configured at the BIOS, so search there. What we get from the above setup is only some graphs from the sensors that already exists at the systems and nothing more. I believe they are reliable since the system does not have other sensors to measure the temperatures. Maybe, when you download with Sabnzbd you get a temp peak and this is what causes the shutdown. Also, 73C is a bit high for average, i believe.

  • Temperature Sensor

    So, I guess, you need both. You need sensors-k10temp-pci-00c3 for temperature (probably you get only CPU temp) and sensors-atk0110-acpi-0 for fan speed etc.
    You should create something like this

    Code
    ...DEF:cpupavg=\${DATA}/sensors-k10temp-pci-00c3/temperature-temp1.rrd:value:AVERAGE \
  DEF:cpupmin=\${DATA}/sensors-k10temp-pci-00c3/temperature-temp1.rrd:value:MIN \
  DEF:cpupmax=\${DATA}/sensors-k10temp-pci-00c3/temperature-temp1.rrd:value:MAX \...


    and something like

    Code
    ...DEF:cpupavg=\${DATA}/sensors-atk0110-acpi-0/fanspeed.rrd:value:AVERAGE \
  DEF:cpupmin=\${DATA}/sensors-atk0110-acpi-0/fanspeed.rrd:value:MIN \
  DEF:cpupmax=\${DATA}/sensors-atk0110-acpi-0/fanspeed.rrd:value:MAX \...


    i guess for the fan speeds

  • Temperature Sensor

    I believe the correct one is k10temp-pci-00c3. You can try

    Code
    cd /var/lib/collectd/rrd/localhost


ls

    and then get inside the folder (probably k10temp-pci-00c3) where you will see, I believe, something like

    Zitat

    temperature-temp1.rrd temperature-temp2.rrd temperature-temp3.rrd


    This is what you must use to edit the file. Hope this helps.

  • Temperature Sensor

    Just a copy from the old forum,http://sourceforge.net/apps/ph…t/viewtopic.php?f=5&t=324, thanks to subzeroin:


    So, I have tried this a little, and this is what I've got (after too many ours of trying to change and compile coretemp.c for the old debian kernel to recognize my i3..).


    First you have to have lm-sensors installed as you covered.


    Log in as root via ssh and use your preferred text-editor (I'll be using vim).


    Code
    vim /var/www/openmediavault/js/omv/module/admin/Sensors.js




    Then I inserted this:





    Then you have to create another file to get your changes in to collectd.conf and omv-mkgraph:


    Code
    vim /usr/share/openmediavault/scripts/collectd.d/sensors




    In this file you probably going to need to edit some things, like what sensors you want to use. I'm using a Intel i3 2100T so my sensors was coretemp:





    Save the file and then you have to make sure it is executable:


    Code
    chmod +x /usr/share/openmediavault/scripts/collectd.d/sensors




    You then run:


    Code
    /usr/share/openmediavault/scripts/collectd




    which is a script that make the collectd.conf and omv-mkgraph file.


    If it doesn't work, try running just


    Code
    /usr/share/openmediavault/scripts/collectd.d/sensors



    and look for errors, if not then try running:


    Code
    omv-mkgraph




    Log in to OMV webgui (or reload if you're already logged in), there should at least be a tab named "CPU temperature" now under SystemInformation->System.


    If you don't know which sensor you have to use in the file we've created before, you can do as this, but first of all, run sensors-detect and load your needed modules.



    Edit the collectd.conf file:


    Code
    vim /etc/collectd/collectd.conf




    Add this row:


    Code
    LoadPlugin sensors




    Reload collectd by either restarting your computer or


    Code
    /etc/init.d/collectd restart




    Now we can try to figure out the sensors and what path collectd uses:


    Zitat

    cd /var/lib/collectd/rrd/localhost


    ls




    Here I got this list:




    We can ignore cpu-0 to cpu-4, df, interface, load and memory since that are standard entries that already is in use by OMV.


    So what is left is sensors-coretemp-isa-0000, now check what's inside that folder:


    Code
    ls sensors-coretemp-isa-0000




    This is what was there, only temps:


    Zitat

    temperature-temp1.rrd temperature-temp2.rrd temperature-temp3.rrd




    And that is what get you what you should use, e.g:


    Zitat

    DEF:cpupavg=\${DATA}/sensors-coretemp-isa-0000/temperature-temp1.rrd:value:AVERAGE




    Another usefull tool is rrdtool, if you get any errors in your scripts just try:



    Code
    rrdtool info yoursensorfile.rrd



    and that will get you a lot of info.


    Hope all this helps :)

    And the changes I made in order to get my sensors working (Asus AT5NM10T-I Atom D525 with sensors-atk0110-acpi-0)


  • Time Characters Unreadable

    Dear Votdev,


    If I am not mistaking when I ran dpkg-reconfigure locale I saw that 2 locales where used, el_GR ISO 8859-7 and el_GR.UTF-8 UTF-8. I remove the first one and then everything where fixed. I hope this answer your question.


    PS Thanks for the help and this great OS :D

  • Time Characters Unreadable

    I managed to solve my problem. It looks like the update created an issue with the locale. First I

    Code
    dpkg-reconfigure locale

    , then

    Code
    choose el_GR.UTF-8

    and finally

    Code
    LANGUAGE="el_GR"

    . After a reboot everythinkg worked great.

  • Time Characters Unreadable

    Dear all,


    Today I updated fro 0.2.7 to 0.3.0.17. Everything was OK exept a problem with Date and Time. Current time is unreadable. I get something like this

    Code
    Êõñ 08 Éïýë 2012 09:10:37 ìì EEST

    I have greek language installed, everything else looks great exept this. Date and time sytem log is also unreadable. At 0.2.7 i did not have any issue. I tried to change the webgui to english but the problem remains. I am sure that this is not a webgui issue but something at the system's settings is wrong, but I do not know how to resolve this. Can anybody help?


    Thank you in advanced,
    John