Author

Topic: [ mining os ] nvoc - page 137. (Read 418546 times)

full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
November 15, 2017, 01:56:04 PM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks


I guess you are the first to report this problem... I expect the forum to be flooded with this same issue soon.

I've been talking about this upcomming problem for a while now... the abuse of logs and recording everything while completely unnecessary.

Recording a log that will eventually fill up all the empty space just to show one line from it in the telegram message is not smart programming... pretty much all the scripts that rely on these logs will have to be rewritten to keep the logs under control.

Devs, if you realy need that log, create a ramdisk (tmpfs) and record screenlog (or whatever other log you need) there and create a cronjob to periodicaly clean it. There's really nothing important from screenlog that needs to be permanently recorded so a, lets say 100 MB ramdisk is perfect solution. Direct the logs there, extract whatever you need when the script is run, then flush the log. Shouldn't be very difficult to do Wink

I heard you mate and started to changing my codes to use named pipes , cant give any ETA, but will do my best to get them ready for next version.
newbie
Activity: 41
Merit: 0
November 15, 2017, 01:53:41 PM
wow, what a cool project!!

Sorry to barge in like this.  I am only on page 7 so far and am sure the answer to my question is in the next 273 pages Wink

Is there a way to run a script or is there a list of things to install on an existing Ubuntu LTS?
My rig is our media center and file share server, but would like to add a dozen cards or so (asus mining expert) to do some mining, as it is idle most of the time.

Thanks
366Cobra


I think its easier to reformat your existing ubuntu and install nvOC then install and set samba, nfs,... and any thing else you need for your media center instead of going through installing and setting up nvOC over an existing ubuntu.

I think his request seems quite interesting to me.
By developing an installable package on a stable "normal" ubuntu (I say normal to mean that this system would only be installed from the ISO provided by cannonical), Fullzero's scripts and all the others could be spread on much more mining rig.
I admit that it is also another work a little wider and tedious, but in fine, the nvOC package could thus be deployed much more widely and probably also on debian or probably other systems.

He would thus make a big competition to ethOS which makes pay his scripts, even if the first goal is not this one, that would perhaps make them review their commercial policy that personally, I find doubtful.
It would probably also bring other linuxians (called "bearded"!) :-) in some circles ha ha! ) to help this very active community of this thread to further optimize scripts and mining software.

Start with a package including software and scripts adapted for an ubuntu and then chained with a debian more classic and less heavy IMO, and observe if this package could interest the other communities of the other banks of Linux like RED HAT, Fedora and / or Mint ... etc.

Would not it be judicious also to reserve this distribution Ubuntu to the beginners with Linux because it is necessary to recognize this to him, ubuntu tries then a few years to convert the workstations windows to Linux.
In my country, it has done rather well to the national gendarmerie! A civil branch of the police.

I think it would be interesting to put these scripts on a system less heavy volume in one way or another.

I hope that what I am trying to express is understandable to some of those who have read this post.

The idea is nice but not quite practical. There are a lot of differences between linux distros and their backbone so such a project would require quite a big team of developers and testers to execute. Just see what happened few weeks back when ubuntu pushed updates... screwed up the operation on single distro, single version.... imagine if we had 6-7 different distros... even the big software companies don't support more than 3-4 main distrubutions of linux.
Different distros handle libraries, drivers, config files differently, not to mention the selection of preinstalled software... it will be impossible to support that from a community driven free project like this

I agree. I wrote just little scripts for a linux app and to get it running with different distros was the most problematic part.
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
November 15, 2017, 01:50:20 PM
Another IAmNotAJeep_and_Maxximus007_WATCHDOG Mod

I had my Verizon FIOS service upgraded the other day and I was unable to shutdown all of my miners before the tech interrupted my internet. This made me scrutinize how the watchdog handles that situation (not very well, IMO) so I made the following modification to just wait on internet service to return rather than just looping, restarting mining, and restarting the host as usual.

Code:

      if [ $COUNT -le 0 ]
      then
# Begin Stubo Mod
# Wait for Internet
         while ! nc -vzw1 google.com 443;
         do
   echo "Internet is down, checking again in 30 seconds..." | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
            sleep 30
         done
#
#         INTERNET_IS_GO=0
#  
#         if nc -vzw1 google.com 443;
#         #if nc -vzw1 $POOL 80;
#         then
#            INTERNET_IS_GO=1
#         fi
         echo ""

#         if [[ $RESTART -gt 4 && $INTERNET_IS_GO == 1 ]]
         if [ $RESTART -gt 4 ]
         # End Stubo Mod
         then
            echo "$(date) - Utilization is too low: reviving did not work so restarting system in 10 seconds" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}


Let me know if you have any questions or see room for improvement in this modification.


I just made some changes to your addition so after checking google for internet it checks coin pool server then it goes for the rest of its job ...
Because I'm not using any dual coin mining and salfter switches I havent gone through the hassle of checking their pool too.

Please check, test and let me know what you think


Code:



  if [ $COUNT -le 0 ]
      then
# Begin Stubo Mod
# Wait for Internet
         while ! nc -vzw1 google.com 443;
         do
   echo "Internet is down, checking again in 30 seconds..." | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
            sleep 30
         done

       # Begin papampi Mod

source /home/m1/1bash

CURRENT_COIN=$(head -n 200 /home/m1/1bash | grep COIN= | sed 's/COIN=//' | sed 's/\"//' | sed 's/\"//')
#echo "$CURRENT_COIN"

CURRENT_COIN_POOL=$(echo {$CURRENT_COIN}_POOL |sed 's/{//' | sed 's/}//' )
#echo $CURRENT_COIN_POOL

POOL_SERVER=$(cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//')
#echo "$POOL_SERVER"

CURRENT_COIN_PORT=$(echo {$CURRENT_COIN}_PORT | sed 's/{//' | sed 's/}//')
#echo "$CURRENT_COIN_PORT"

if [[ $POOL_SERVER == *stratum* ]]
then
    #echo "stratum"
    PING_SERVER=$( cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//' | sed 's/stratum+tcp\?:\/\///' | cut -d':' -f1 )
    #echo "Server: $PING_SERVER"
    PING_PORT=$(cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//' | sed 's/stratum+tcp\?:\/\///' | grep -Eo '[0-9]+$' )
    #echo "Port: $PING_PORT"    

if nc -vzw2 $PING_SERVER $PING_PORT;
    then
        # echo "Strartum Server, INTERNET_IS_GO=1"
        INTERNET_IS_GO=1
    else
        echo "WARNING:  $(date) - Mining Pool Stratum Server is DOWN" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
        INTERNET_IS_GO=0
    fi
    
elif [[ $CURRENT_COIN == *DUAL*  || $CURRENT_COIN == *ZPOOL_SKUNK* || $CURRENT_COIN == *SALFTER*  ]]
then
    #echo "Dual mining, check google"
    if nc -vzw2 google.com 443
    then
        # echo "Dual mining, google is up"
        #echo "            INTERNET_IS_GO=1"
        INTERNET_IS_GO=1
    else
        #echo "Dual mining, google is down"
        echo "WARNING:  $(date) - Cant reach google" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
        INTERNET_IS_GO=0
    fi
    
else
      PING_SERVER=$( cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//')
      #echo "Server: $PING_SERVER"
      PING_PORT=$(cat /home/m1/1bash | grep $CURRENT_COIN_PORT | grep -o '".*"' | sed 's/"//' |sed 's/"//')
      #echo "Port: $PING_PORT"
      if nc -vzw1 $PING_SERVER $PING_PORT
    then
        #echo "Not a stratum server,INTERNET_IS_GO=1" | tee -a ${LOG_FILE}
        INTERNET_IS_GO=1
    else
        echo "WARNING:  $(date) - Mining Pool Server is DOWN" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
        INTERNET_IS_GO=0
    fi
fi


       # End papampi Mod


#         INTERNET_IS_GO=0
 
#         if nc -vzw1 google.com 443;
#         #if nc -vzw1 $POOL 80;
#         then
#            INTERNET_IS_GO=1
#         fi
         echo ""

         if [[ $RESTART -gt 4 && $INTERNET_IS_GO == 1 ]]
#         if [ $RESTART -gt 4 ]
         # End Stubo Mod
         then
            echo "$(date) - Utilization is too low: reviving did not work so restarting system in 10 seconds" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}




Edited to add server port too.

Sorry, I don't like this at all. You are making a lot of assumptions there and, IMO, mucking up an already confusing script with logic is doesn't need. First you are assuming that folks are using your autoswitch and I think some/most are not. I tried it, it worked, but mining that way (most profitable at the time) doesn't fit my personal mining philosophy. When I make modifications that I share with others, they are ones that generally everyone would appreciate. For example, faster down miner restarts, and better handling of internet down condition. While I appreciate that you are trying to make the watchdog better by detecting if the pool is down, I think that is just too difficult given how many different types of mining configurations are supported by nvOC. Besides that, pools being down are not a common occurrence in my personal, but limited, experience.

That being said, I think this type of modification is fine as a personal one. I just really don't think it is something that most users of nvOC would need. Instead, I think it could cause more problems than it resolves.

Just my 2 cents as always...

I noticed a commented out pool check from fullzero and remembered he once said he wanted to add it to wdog when a while back one of the pools went down and caused a massive number of users get so many reboots, I myself was one of them, so I thought it could be a good addition to wdog.
And yes there are so many different types of mining configuration in nvOC but I think there is only 2 types of server usage in the miners and what I wrote covers both (server:port or --server --port )

Dont know whats checking if pool is online or not for wdog before restart miner and get to rebooting loop has to do with wtm auto switch though ... seems you are mixing 2 different things together.
I wrote wtm auto switch for my own usage and shared it with the community the same as I done with other stuff and I will keep sharing and dont care if only one person use it or all.

Thanks for your input any way  Wink
full member
Activity: 200
Merit: 101
November 15, 2017, 01:38:50 PM
wow, what a cool project!!

Sorry to barge in like this.  I am only on page 7 so far and am sure the answer to my question is in the next 273 pages Wink

Is there a way to run a script or is there a list of things to install on an existing Ubuntu LTS?
My rig is our media center and file share server, but would like to add a dozen cards or so (asus mining expert) to do some mining, as it is idle most of the time.

Thanks
366Cobra


I think its easier to reformat your existing ubuntu and install nvOC then install and set samba, nfs,... and any thing else you need for your media center instead of going through installing and setting up nvOC over an existing ubuntu.

I think his request seems quite interesting to me.
By developing an installable package on a stable "normal" ubuntu (I say normal to mean that this system would only be installed from the ISO provided by cannonical), Fullzero's scripts and all the others could be spread on much more mining rig.
I admit that it is also another work a little wider and tedious, but in fine, the nvOC package could thus be deployed much more widely and probably also on debian or probably other systems.

He would thus make a big competition to ethOS which makes pay his scripts, even if the first goal is not this one, that would perhaps make them review their commercial policy that personally, I find doubtful.
It would probably also bring other linuxians (called "bearded"!) :-) in some circles ha ha! ) to help this very active community of this thread to further optimize scripts and mining software.

Start with a package including software and scripts adapted for an ubuntu and then chained with a debian more classic and less heavy IMO, and observe if this package could interest the other communities of the other banks of Linux like RED HAT, Fedora and / or Mint ... etc.

Would not it be judicious also to reserve this distribution Ubuntu to the beginners with Linux because it is necessary to recognize this to him, ubuntu tries then a few years to convert the workstations windows to Linux.
In my country, it has done rather well to the national gendarmerie! A civil branch of the police.

I think it would be interesting to put these scripts on a system less heavy volume in one way or another.

I hope that what I am trying to express is understandable to some of those who have read this post.

The idea is nice but not quite practical. There are a lot of differences between linux distros and their backbone so such a project would require quite a big team of developers and testers to execute. Just see what happened few weeks back when ubuntu pushed updates... screwed up the operation on single distro, single version.... imagine if we had 6-7 different distros... even the big software companies don't support more than 3-4 main distrubutions of linux.
Different distros handle libraries, drivers, config files differently, not to mention the selection of preinstalled software... it will be impossible to support that from a community driven free project like this
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
November 15, 2017, 01:09:47 PM
wow, what a cool project!!

Sorry to barge in like this.  I am only on page 7 so far and am sure the answer to my question is in the next 273 pages Wink

Is there a way to run a script or is there a list of things to install on an existing Ubuntu LTS?
My rig is our media center and file share server, but would like to add a dozen cards or so (asus mining expert) to do some mining, as it is idle most of the time.

Thanks
366Cobra


I think its easier to reformat your existing ubuntu and install nvOC then install and set samba, nfs,... and any thing else you need for your media center instead of going through installing and setting up nvOC over an existing ubuntu.

I think his request seems quite interesting to me.
By developing an installable package on a stable "normal" ubuntu (I say normal to mean that this system would only be installed from the ISO provided by cannonical), Fullzero's scripts and all the others could be spread on much more mining rig.
I admit that it is also another work a little wider and tedious, but in fine, the nvOC package could thus be deployed much more widely and probably also on debian or probably other systems.

He would thus make a big competition to ethOS which makes pay his scripts, even if the first goal is not this one, that would perhaps make them review their commercial policy that personally, I find doubtful.
It would probably also bring other linuxians (called "bearded"!) :-) in some circles ha ha! ) to help this very active community of this thread to further optimize scripts and mining software.

Start with a package including software and scripts adapted for an ubuntu and then chained with a debian more classic and less heavy IMO, and observe if this package could interest the other communities of the other banks of Linux like RED HAT, Fedora and / or Mint ... etc.

Would not it be judicious also to reserve this distribution Ubuntu to the beginners with Linux because it is necessary to recognize this to him, ubuntu tries then a few years to convert the workstations windows to Linux.
In my country, it has done rather well to the national gendarmerie! A civil branch of the police.

I think it would be interesting to put these scripts on a system less heavy volume in one way or another.

I hope that what I am trying to express is understandable to some of those who have read this post.
member
Activity: 224
Merit: 13
November 15, 2017, 11:44:38 AM
Another IAmNotAJeep_and_Maxximus007_WATCHDOG Mod

I had my Verizon FIOS service upgraded the other day and I was unable to shutdown all of my miners before the tech interrupted my internet. This made me scrutinize how the watchdog handles that situation (not very well, IMO) so I made the following modification to just wait on internet service to return rather than just looping, restarting mining, and restarting the host as usual.

Code:

      if [ $COUNT -le 0 ]
      then
# Begin Stubo Mod
# Wait for Internet
         while ! nc -vzw1 google.com 443;
         do
   echo "Internet is down, checking again in 30 seconds..." | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
            sleep 30
         done
#
#         INTERNET_IS_GO=0
#  
#         if nc -vzw1 google.com 443;
#         #if nc -vzw1 $POOL 80;
#         then
#            INTERNET_IS_GO=1
#         fi
         echo ""

#         if [[ $RESTART -gt 4 && $INTERNET_IS_GO == 1 ]]
         if [ $RESTART -gt 4 ]
         # End Stubo Mod
         then
            echo "$(date) - Utilization is too low: reviving did not work so restarting system in 10 seconds" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}


Let me know if you have any questions or see room for improvement in this modification.


I just made some changes to your addition so after checking google for internet it checks coin pool server then it goes for the rest of its job ...
Because I'm not using any dual coin mining and salfter switches I havent gone through the hassle of checking their pool too.

Please check, test and let me know what you think


Code:



  if [ $COUNT -le 0 ]
      then
# Begin Stubo Mod
# Wait for Internet
         while ! nc -vzw1 google.com 443;
         do
   echo "Internet is down, checking again in 30 seconds..." | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
            sleep 30
         done

       # Begin papampi Mod

source /home/m1/1bash

CURRENT_COIN=$(head -n 200 /home/m1/1bash | grep COIN= | sed 's/COIN=//' | sed 's/\"//' | sed 's/\"//')
#echo "$CURRENT_COIN"

CURRENT_COIN_POOL=$(echo {$CURRENT_COIN}_POOL |sed 's/{//' | sed 's/}//' )
#echo $CURRENT_COIN_POOL

POOL_SERVER=$(cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//')
#echo "$POOL_SERVER"

CURRENT_COIN_PORT=$(echo {$CURRENT_COIN}_PORT | sed 's/{//' | sed 's/}//')
#echo "$CURRENT_COIN_PORT"

if [[ $POOL_SERVER == *stratum* ]]
then
    #echo "stratum"
    PING_SERVER=$( cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//' | sed 's/stratum+tcp\?:\/\///' | cut -d':' -f1 )
    #echo "Server: $PING_SERVER"
    PING_PORT=$(cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//' | sed 's/stratum+tcp\?:\/\///' | grep -Eo '[0-9]+$' )
    #echo "Port: $PING_PORT"    

if nc -vzw2 $PING_SERVER $PING_PORT;
    then
        # echo "Strartum Server, INTERNET_IS_GO=1"
        INTERNET_IS_GO=1
    else
        echo "WARNING:  $(date) - Mining Pool Stratum Server is DOWN" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
        INTERNET_IS_GO=0
    fi
    
elif [[ $CURRENT_COIN == *DUAL*  || $CURRENT_COIN == *ZPOOL_SKUNK* || $CURRENT_COIN == *SALFTER*  ]]
then
    #echo "Dual mining, check google"
    if nc -vzw2 google.com 443
    then
        # echo "Dual mining, google is up"
        #echo "            INTERNET_IS_GO=1"
        INTERNET_IS_GO=1
    else
        #echo "Dual mining, google is down"
        echo "WARNING:  $(date) - Cant reach google" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
        INTERNET_IS_GO=0
    fi
    
else
      PING_SERVER=$( cat /home/m1/1bash | grep $CURRENT_COIN_POOL | grep -o '".*"' | sed 's/"//'| sed 's/"//')
      #echo "Server: $PING_SERVER"
      PING_PORT=$(cat /home/m1/1bash | grep $CURRENT_COIN_PORT | grep -o '".*"' | sed 's/"//' |sed 's/"//')
      #echo "Port: $PING_PORT"
      if nc -vzw1 $PING_SERVER $PING_PORT
    then
        #echo "Not a stratum server,INTERNET_IS_GO=1" | tee -a ${LOG_FILE}
        INTERNET_IS_GO=1
    else
        echo "WARNING:  $(date) - Mining Pool Server is DOWN" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}
        INTERNET_IS_GO=0
    fi
fi


       # End papampi Mod


#         INTERNET_IS_GO=0
 
#         if nc -vzw1 google.com 443;
#         #if nc -vzw1 $POOL 80;
#         then
#            INTERNET_IS_GO=1
#         fi
         echo ""

         if [[ $RESTART -gt 4 && $INTERNET_IS_GO == 1 ]]
#         if [ $RESTART -gt 4 ]
         # End Stubo Mod
         then
            echo "$(date) - Utilization is too low: reviving did not work so restarting system in 10 seconds" | tee -a ${LOG_FILE} ${ALERT_LOG_FILE}




Edited to add server port too.

Sorry, I don't like this at all. You are making a lot of assumptions there and, IMO, mucking up an already confusing script with logic is doesn't need. First you are assuming that folks are using your autoswitch and I think some/most are not. I tried it, it worked, but mining that way (most profitable at the time) doesn't fit my personal mining philosophy. When I make modifications that I share with others, they are ones that generally everyone would appreciate. For example, faster down miner restarts, and better handling of internet down condition. While I appreciate that you are trying to make the watchdog better by detecting if the pool is down, I think that is just too difficult given how many different types of mining configurations are supported by nvOC. Besides that, pools being down are not a common occurrence in my personal, but limited, experience.

That being said, I think this type of modification is fine as a personal one. I just really don't think it is something that most users of nvOC would need. Instead, I think it could cause more problems than it resolves.

Just my 2 cents as always...
member
Activity: 117
Merit: 10
November 15, 2017, 11:40:42 AM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks


Thats the miner output log , but cant be 6 GB, Some thing is not right

You can set clear logs on reboot in 1bash

When you record whole output from the miner 24/7 it sure can reach 6 GB in a week or two... or even sooner, no surprise there

Mining etc for 3 weeks (13 gpus rig non stop) let me a 128Mg file using Claymore. I still think 6Gb its too much
member
Activity: 117
Merit: 10
November 15, 2017, 11:38:27 AM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks


I guess you are the first to report this problem... I expect the forum to be flooded with this same issue soon.

I've been talking about this upcomming problem for a while now... the abuse of logs and recording everything while completely unnecessary.

Recording a log that will eventually fill up all the empty space just to show one line from it in the telegram message is not smart programming... pretty much all the scripts that rely on these logs will have to be rewritten to keep the logs under control.

Devs, if you realy need that log, create a ramdisk (tmpfs) and record screenlog (or whatever other log you need) there and create a cronjob to periodicaly clean it. There's really nothing important from screenlog that needs to be permanently recorded so a, lets say 100 MB ramdisk is perfect solution. Direct the logs there, extract whatever you need when the script is run, then flush the log. Shouldn't be very difficult to do Wink

I quite agree with you.
In any case:
Code:
screen -dr miner -X logfile custom_log_file_name.log

change the log file name to "custom_log_file_name.log"

Code:
screen -dr miner -X log    # Start login miner

sleep some_seconds        # wait at least 12 secs for screen to write the buffer to log file

# Code and things you want to do
.....
.....
.....
.....

screen -dr miner -X log    # Stop login miner

No need to use the -L flag anymore.
full member
Activity: 200
Merit: 101
November 15, 2017, 11:30:31 AM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks


Thats the miner output log , but cant be 6 GB, Some thing is not right

You can set clear logs on reboot in 1bash

When you record whole output from the miner 24/7 it sure can reach 6 GB in a week or two... or even sooner, no surprise there
full member
Activity: 200
Merit: 101
November 15, 2017, 11:27:46 AM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks


I guess you are the first to report this problem... I expect the forum to be flooded with this same issue soon.

I've been talking about this upcomming problem for a while now... the abuse of logs and recording everything while completely unnecessary.

Recording a log that will eventually fill up all the empty space just to show one line from it in the telegram message is not smart programming... pretty much all the scripts that rely on these logs will have to be rewritten to keep the logs under control.

Devs, if you realy need that log, create a ramdisk (tmpfs) and record screenlog (or whatever other log you need) there and create a cronjob to periodicaly clean it. There's really nothing important from screenlog that needs to be permanently recorded so a, lets say 100 MB ramdisk is perfect solution. Direct the logs there, extract whatever you need when the script is run, then flush the log. Shouldn't be very difficult to do Wink
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
November 15, 2017, 11:24:24 AM
Thanks. I did set it to clear on reboot but I rarely reboot. I am often away from my machines for weeks at a time.

This file was definitely 6gb in just two days of use. I did a df on my other 5 rigs and they are all fine. It was just this new one. I will monitor it.




My rig is up for more than a week and I have not set to clear logs and my screenlog.0 is about 11Mb


Code:
m1@m1-desktop-101:~$ ll screenlog.0
-rw-rw-r-- 1 m1 m1 11847254 Nov 15 19:51 screenlog.0
member
Activity: 117
Merit: 10
November 15, 2017, 11:16:58 AM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks


To stop screen from creating the log file you are taking about remove the "L" flag in the screen lines in 3main file, so the screen order will go from this:
Code:
screen -dmSL miner .... etc, etc, etc

to this:
Code:
screen -dmS miner .... etc, etc, etc

But keep in main that some scripts expects to find that log file and if you remove it you may lose some info in your reports.

Other way to solve it would be to use logrotate to compress and keep/delete the file.
You can too run a order from cron and empty the file every some time.
Let me know if you have trouble with any of those.
And I must agreed with Papampi, its a very big file, it should'n be so big.  
full member
Activity: 132
Merit: 100
November 15, 2017, 11:14:43 AM
Thanks. I did set it to clear on reboot but I rarely reboot. I am often away from my machines for weeks at a time.

This file was definitely 6gb in just two days of use. I did a df on my other 5 rigs and they are all fine. It was just this new one. I will monitor it.
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
November 15, 2017, 10:51:05 AM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks


Thats the miner output log , but cant be 6 GB, Some thing is not right

You can set clear logs on reboot in 1bash
member
Activity: 96
Merit: 10
November 15, 2017, 10:32:28 AM

Glad it worked for you, happy to help, you are welcome.

Changes; have you improved hashrate?  Grin

If so please share it with us  Roll Eyes

Little to no difference Sad So I dont think u want my version Cheesy
full member
Activity: 132
Merit: 100
November 15, 2017, 10:19:24 AM
I have 5 rigs running on 19, and set up my first on the 19.4 two days ago. This morning I tried to make a change to 1bash and it would not let me because of no disk space.

I did some searching and found a 6.4 GB file sreenlog.0 I deleted it and then tried to nano 1 bash and it gave an error about a 1bash.swp lock file. I used VI and was able to delete the sap file and now nano works and I edited the 1 bash.

What is up with this huge screen log.0 file and how can I keep it from creating this?

Thanks
full member
Activity: 378
Merit: 104
nvOC forever
November 15, 2017, 10:01:57 AM
i keep the power limit at 75 untouch
i did -i 21 before, rig stop after few hour

Ah ok, its better to let it run on 19 then, probably I should try as well.

Coming to power limit, i have checked, its not using much anyway, so doesn't matter how much we limit it to (as long as its not lower than what it is currently using).

Thanks.

BSD is looking good to me, may i know which coin you mining in?

HAHAHA I mine so many coins with my one only one RIG, currently mining BSD, was mining SMART thinking of SUMO and what not Cheesy
member
Activity: 82
Merit: 10
November 15, 2017, 09:20:28 AM
i keep the power limit at 75 untouch
i did -i 21 before, rig stop after few hour

Ah ok, its better to let it run on 19 then, probably I should try as well.

Coming to power limit, i have checked, its not using much anyway, so doesn't matter how much we limit it to (as long as its not lower than what it is currently using).

Thanks.

BSD is looking good to me, may i know which coin you mining in?
full member
Activity: 378
Merit: 104
nvOC forever
November 15, 2017, 09:13:35 AM
full member
Activity: 378
Merit: 104
nvOC forever
November 15, 2017, 09:11:46 AM
i keep the power limit at 75 untouch
i did -i 21 before, rig stop after few hour

Ah ok, its better to let it run on 19 then, probably I should try as well.

Coming to power limit, i have checked, its not using much anyway, so doesn't matter how much we limit it to (as long as its not lower than what it is currently using).

Thanks.
Jump to: