iSCSI and runaway log fileiptables log fileHow to log to file and to consoleiSCSI on startupLog file not...

Why should password hash verification be time constant?

Why did Captain America age?

cropping a message using array splits

Why do Thanos' punches not kill Captain America or at least cause vital wounds?

How to get a ellipse shaped node in Tikz Network?

Why can't I prove summation identities without guessing?

Can 'sudo apt-get remove [write]' destroy my Ubuntu?

No such column 'DeveloperName' on entity 'RecordType' after Summer '19 release on sandbox

Is there an application which does HTTP PUT?

How to evaluate sum with one million summands?

Series that evaluates to different values upon changing order of summation

How to handle DM constantly stealing everything from sleeping characters?

Has magnetic core memory been used beyond the Moon?

How to select certain lines (n, n+4, n+8, n+12...) from the file?

Exception propagation: When to catch exceptions?

Watching the game, having a puzzle

My perfect evil overlord plan... or is it?

Why use steam instead of just hot air?

How to get the IP of a user who executed a command?

Is it nonsense to say B -> [A -> B]?

Company stopped paying my salary. What are my options?

We are two immediate neighbors who forged our own powers to form concatenated relationship. Who are we?

Why does increasing the sampling rate make implementing an anti-aliasing filter easier?

Is this state of Earth possible, after humans left for a million years?



iSCSI and runaway log file


iptables log fileHow to log to file and to consoleiSCSI on startupLog file not growing beyond a size. Why?How to clean log file?How to permanantly disable /var/log/secure?(CentOS) default FTP (SFTP) Log File?Does /var/log/secure log successes?How to write and handle custom log file properly?Daily Log Files from Single Log File






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















I have a OpenVZ VPS running CentOS 5.7 that I've been using to get some sysadmin experience.



I found a log file called brcm-iscsi.log in /var/log and it's getting big (140 MB).



INFO  [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
INFO [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
WARN [Sun Dec 18 20:15:42 2011]nic_utils Error when scanning path: /sys/class/iscsi_host/[No such file or directory]
INFO [Sun Dec 18 20:15:42 2011]signal handling thread ready
ERR [Sun Dec 18 20:15:42 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
ERR [Sun Dec 18 20:15:43 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
ERR [Sun Dec 18 20:15:44 2011]NIC_NL waiting binding to NETLINK_ISCSI socket


And every second since then I've had that line. I don't quite understand what is going on, so I'm hoping someone could tell me how to fix the underlying problem rather than just deleting the log file. I did Google this and found http://drup.org/brcm-iscsilog-filling-hard-drive which seems to just disable iSCSI and ignore any more errors. Is there a better/safer/preferable way of stopping this error logging?



I don't know much about iSCSI - I get that it's a SAN protocol, but that's about it. I've certainly never setup any volumes outside of the disk space I got with my VPS. Could my VPS be relying on this in some way? I wouldn't want to trash it, although I'm getting quite practiced at reloading the VPS... I also wouldn't want to screw up anyone else's nodes.










share|improve this question































    2















    I have a OpenVZ VPS running CentOS 5.7 that I've been using to get some sysadmin experience.



    I found a log file called brcm-iscsi.log in /var/log and it's getting big (140 MB).



    INFO  [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
    INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
    INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
    INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
    INFO [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
    INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
    INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
    INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
    WARN [Sun Dec 18 20:15:42 2011]nic_utils Error when scanning path: /sys/class/iscsi_host/[No such file or directory]
    INFO [Sun Dec 18 20:15:42 2011]signal handling thread ready
    ERR [Sun Dec 18 20:15:42 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
    ERR [Sun Dec 18 20:15:43 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
    ERR [Sun Dec 18 20:15:44 2011]NIC_NL waiting binding to NETLINK_ISCSI socket


    And every second since then I've had that line. I don't quite understand what is going on, so I'm hoping someone could tell me how to fix the underlying problem rather than just deleting the log file. I did Google this and found http://drup.org/brcm-iscsilog-filling-hard-drive which seems to just disable iSCSI and ignore any more errors. Is there a better/safer/preferable way of stopping this error logging?



    I don't know much about iSCSI - I get that it's a SAN protocol, but that's about it. I've certainly never setup any volumes outside of the disk space I got with my VPS. Could my VPS be relying on this in some way? I wouldn't want to trash it, although I'm getting quite practiced at reloading the VPS... I also wouldn't want to screw up anyone else's nodes.










    share|improve this question



























      2












      2








      2








      I have a OpenVZ VPS running CentOS 5.7 that I've been using to get some sysadmin experience.



      I found a log file called brcm-iscsi.log in /var/log and it's getting big (140 MB).



      INFO  [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
      INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
      INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
      INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
      INFO [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
      INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
      INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
      INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
      WARN [Sun Dec 18 20:15:42 2011]nic_utils Error when scanning path: /sys/class/iscsi_host/[No such file or directory]
      INFO [Sun Dec 18 20:15:42 2011]signal handling thread ready
      ERR [Sun Dec 18 20:15:42 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
      ERR [Sun Dec 18 20:15:43 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
      ERR [Sun Dec 18 20:15:44 2011]NIC_NL waiting binding to NETLINK_ISCSI socket


      And every second since then I've had that line. I don't quite understand what is going on, so I'm hoping someone could tell me how to fix the underlying problem rather than just deleting the log file. I did Google this and found http://drup.org/brcm-iscsilog-filling-hard-drive which seems to just disable iSCSI and ignore any more errors. Is there a better/safer/preferable way of stopping this error logging?



      I don't know much about iSCSI - I get that it's a SAN protocol, but that's about it. I've certainly never setup any volumes outside of the disk space I got with my VPS. Could my VPS be relying on this in some way? I wouldn't want to trash it, although I'm getting quite practiced at reloading the VPS... I also wouldn't want to screw up anyone else's nodes.










      share|improve this question
















      I have a OpenVZ VPS running CentOS 5.7 that I've been using to get some sysadmin experience.



      I found a log file called brcm-iscsi.log in /var/log and it's getting big (140 MB).



      INFO  [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
      INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
      INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
      INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
      INFO [Sun Dec 18 20:15:42 2011]Initialize logger using log file: /var/log/brcm-iscsi.log
      INFO [Sun Dec 18 20:15:42 2011]Started BRCM iSCSI stack: Ver 0.6.2.13
      INFO [Sun Dec 18 20:15:42 2011]Build date: Fri Jul 22 01:19:02 EDT 2011
      INFO [Sun Dec 18 20:15:42 2011]Running on sysname: 'Linux', release: '2.6.18-274.7.1.el5.028stab095.1', version '#1 SMP Mon Oct 24 20:49:24 MSD 2011' machine: 'i686'
      WARN [Sun Dec 18 20:15:42 2011]nic_utils Error when scanning path: /sys/class/iscsi_host/[No such file or directory]
      INFO [Sun Dec 18 20:15:42 2011]signal handling thread ready
      ERR [Sun Dec 18 20:15:42 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
      ERR [Sun Dec 18 20:15:43 2011]NIC_NL waiting binding to NETLINK_ISCSI socket
      ERR [Sun Dec 18 20:15:44 2011]NIC_NL waiting binding to NETLINK_ISCSI socket


      And every second since then I've had that line. I don't quite understand what is going on, so I'm hoping someone could tell me how to fix the underlying problem rather than just deleting the log file. I did Google this and found http://drup.org/brcm-iscsilog-filling-hard-drive which seems to just disable iSCSI and ignore any more errors. Is there a better/safer/preferable way of stopping this error logging?



      I don't know much about iSCSI - I get that it's a SAN protocol, but that's about it. I've certainly never setup any volumes outside of the disk space I got with my VPS. Could my VPS be relying on this in some way? I wouldn't want to trash it, although I'm getting quite practiced at reloading the VPS... I also wouldn't want to screw up anyone else's nodes.







      centos logs






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 3 hours ago









      Rui F Ribeiro

      42.7k1486146




      42.7k1486146










      asked Jan 9 '12 at 19:08









      BigglesBiggles

      6328




      6328






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Google it and you come up with plenty links (Check out this one, for instance https://groups.google.com/forum/#!topic/open-iscsi/S3ps_mqzd_k) If you do not know what iscsi is (basically, SCSI over the wire: low level access to network disks) chances are good you won't be using it any time soon so you can remove/stop all the related cruft.






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f28693%2fiscsi-and-runaway-log-file%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Google it and you come up with plenty links (Check out this one, for instance https://groups.google.com/forum/#!topic/open-iscsi/S3ps_mqzd_k) If you do not know what iscsi is (basically, SCSI over the wire: low level access to network disks) chances are good you won't be using it any time soon so you can remove/stop all the related cruft.






            share|improve this answer




























              0














              Google it and you come up with plenty links (Check out this one, for instance https://groups.google.com/forum/#!topic/open-iscsi/S3ps_mqzd_k) If you do not know what iscsi is (basically, SCSI over the wire: low level access to network disks) chances are good you won't be using it any time soon so you can remove/stop all the related cruft.






              share|improve this answer


























                0












                0








                0







                Google it and you come up with plenty links (Check out this one, for instance https://groups.google.com/forum/#!topic/open-iscsi/S3ps_mqzd_k) If you do not know what iscsi is (basically, SCSI over the wire: low level access to network disks) chances are good you won't be using it any time soon so you can remove/stop all the related cruft.






                share|improve this answer













                Google it and you come up with plenty links (Check out this one, for instance https://groups.google.com/forum/#!topic/open-iscsi/S3ps_mqzd_k) If you do not know what iscsi is (basically, SCSI over the wire: low level access to network disks) chances are good you won't be using it any time soon so you can remove/stop all the related cruft.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 10 '12 at 16:13









                Alien Life FormAlien Life Form

                521312




                521312






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f28693%2fiscsi-and-runaway-log-file%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                    Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                    Ciclooctatetraenă Vezi și | Bibliografie | Meniu de navigare637866text4148569-500570979m