Centos 7 - cups-pdf postprocessing script running but no result











up vote
0
down vote

favorite












I got an issue using the postprocessing in cups-pdf.
The script is called as I can see in the log files, but nothing happens.



/var/log/cups/cups-pdf-myPrinter_log:



Thu Jun 15 10:07:11 2017  [DEBUG] postprocessing commandline built: /etc/cups/postprocessing/ppmyPrinter.sh /srv/samba/cups-pdf/myPrinter/user/000012198600001.pdf user@dom.local user
Thu Jun 15 10:07:11 2017 [DEBUG] postprocessing has finished: 32256


vim /etc/cups/cups-pdf-myPrinter.conf



PostProcessing /etc/cups/postprocessing/ppmyPrinter.sh


-rwxrwxrwx 1 root lp 194 Jun 15 09:35 ppmyPrinter.sh



vim /etc/cups/postprocessing/ppmyPrinter.sh



#!/bin/bash

echo "$1" >> /etc/cups/postprocessing/user
echo "$2" >> /etc/cups/postprocessing/user
echo "$3" >> /etc/cups/postprocessing/user


if I run the script ./ppmyPrinter.sh test1 test2 test3 it creates the file user with the content test1 test2 test3 but by calling from cups nothing happens.
I red, that on a debian based system (ubuntu) cups-pdf is watched by apparmor and I have to permit to execute the script, but on my CentOs 7 there is no apparmor running.



Could you give me a hint, where to look for this issue, are there som log-files where I can see the problem?










share|improve this question




























    up vote
    0
    down vote

    favorite












    I got an issue using the postprocessing in cups-pdf.
    The script is called as I can see in the log files, but nothing happens.



    /var/log/cups/cups-pdf-myPrinter_log:



    Thu Jun 15 10:07:11 2017  [DEBUG] postprocessing commandline built: /etc/cups/postprocessing/ppmyPrinter.sh /srv/samba/cups-pdf/myPrinter/user/000012198600001.pdf user@dom.local user
    Thu Jun 15 10:07:11 2017 [DEBUG] postprocessing has finished: 32256


    vim /etc/cups/cups-pdf-myPrinter.conf



    PostProcessing /etc/cups/postprocessing/ppmyPrinter.sh


    -rwxrwxrwx 1 root lp 194 Jun 15 09:35 ppmyPrinter.sh



    vim /etc/cups/postprocessing/ppmyPrinter.sh



    #!/bin/bash

    echo "$1" >> /etc/cups/postprocessing/user
    echo "$2" >> /etc/cups/postprocessing/user
    echo "$3" >> /etc/cups/postprocessing/user


    if I run the script ./ppmyPrinter.sh test1 test2 test3 it creates the file user with the content test1 test2 test3 but by calling from cups nothing happens.
    I red, that on a debian based system (ubuntu) cups-pdf is watched by apparmor and I have to permit to execute the script, but on my CentOs 7 there is no apparmor running.



    Could you give me a hint, where to look for this issue, are there som log-files where I can see the problem?










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I got an issue using the postprocessing in cups-pdf.
      The script is called as I can see in the log files, but nothing happens.



      /var/log/cups/cups-pdf-myPrinter_log:



      Thu Jun 15 10:07:11 2017  [DEBUG] postprocessing commandline built: /etc/cups/postprocessing/ppmyPrinter.sh /srv/samba/cups-pdf/myPrinter/user/000012198600001.pdf user@dom.local user
      Thu Jun 15 10:07:11 2017 [DEBUG] postprocessing has finished: 32256


      vim /etc/cups/cups-pdf-myPrinter.conf



      PostProcessing /etc/cups/postprocessing/ppmyPrinter.sh


      -rwxrwxrwx 1 root lp 194 Jun 15 09:35 ppmyPrinter.sh



      vim /etc/cups/postprocessing/ppmyPrinter.sh



      #!/bin/bash

      echo "$1" >> /etc/cups/postprocessing/user
      echo "$2" >> /etc/cups/postprocessing/user
      echo "$3" >> /etc/cups/postprocessing/user


      if I run the script ./ppmyPrinter.sh test1 test2 test3 it creates the file user with the content test1 test2 test3 but by calling from cups nothing happens.
      I red, that on a debian based system (ubuntu) cups-pdf is watched by apparmor and I have to permit to execute the script, but on my CentOs 7 there is no apparmor running.



      Could you give me a hint, where to look for this issue, are there som log-files where I can see the problem?










      share|improve this question















      I got an issue using the postprocessing in cups-pdf.
      The script is called as I can see in the log files, but nothing happens.



      /var/log/cups/cups-pdf-myPrinter_log:



      Thu Jun 15 10:07:11 2017  [DEBUG] postprocessing commandline built: /etc/cups/postprocessing/ppmyPrinter.sh /srv/samba/cups-pdf/myPrinter/user/000012198600001.pdf user@dom.local user
      Thu Jun 15 10:07:11 2017 [DEBUG] postprocessing has finished: 32256


      vim /etc/cups/cups-pdf-myPrinter.conf



      PostProcessing /etc/cups/postprocessing/ppmyPrinter.sh


      -rwxrwxrwx 1 root lp 194 Jun 15 09:35 ppmyPrinter.sh



      vim /etc/cups/postprocessing/ppmyPrinter.sh



      #!/bin/bash

      echo "$1" >> /etc/cups/postprocessing/user
      echo "$2" >> /etc/cups/postprocessing/user
      echo "$3" >> /etc/cups/postprocessing/user


      if I run the script ./ppmyPrinter.sh test1 test2 test3 it creates the file user with the content test1 test2 test3 but by calling from cups nothing happens.
      I red, that on a debian based system (ubuntu) cups-pdf is watched by apparmor and I have to permit to execute the script, but on my CentOs 7 there is no apparmor running.



      Could you give me a hint, where to look for this issue, are there som log-files where I can see the problem?







      centos cups






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 15 '17 at 10:58

























      asked Jun 15 '17 at 8:58









      Eldo.Ob

      1014




      1014






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          On CentOS you have to deal with SELinux instead of AppArmor, if this might be an issue. Check your SELinux status by getenforce. If it is Enabled, inspect the /var/log/audit/audit.log file.






          share|improve this answer





















          • # getenforce - Disabled I also checked the audit files but nothing to see there, also if I tail the audit.log and create a print job. :(
            – Eldo.Ob
            Jun 15 '17 at 10:20


















          up vote
          0
          down vote













          In CentOS there is another setting that causes the same symptoms. The post processing script runs as "nobody" user by default, so you must to add a line in the /etc/sudoers file to allow the script to run without prompting for a password:



          nobody ALL=(ALL) NOPASSWD:/yourpath/yourscript.sh






          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',
            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%2f371273%2fcentos-7-cups-pdf-postprocessing-script-running-but-no-result%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            On CentOS you have to deal with SELinux instead of AppArmor, if this might be an issue. Check your SELinux status by getenforce. If it is Enabled, inspect the /var/log/audit/audit.log file.






            share|improve this answer





















            • # getenforce - Disabled I also checked the audit files but nothing to see there, also if I tail the audit.log and create a print job. :(
              – Eldo.Ob
              Jun 15 '17 at 10:20















            up vote
            0
            down vote













            On CentOS you have to deal with SELinux instead of AppArmor, if this might be an issue. Check your SELinux status by getenforce. If it is Enabled, inspect the /var/log/audit/audit.log file.






            share|improve this answer





















            • # getenforce - Disabled I also checked the audit files but nothing to see there, also if I tail the audit.log and create a print job. :(
              – Eldo.Ob
              Jun 15 '17 at 10:20













            up vote
            0
            down vote










            up vote
            0
            down vote









            On CentOS you have to deal with SELinux instead of AppArmor, if this might be an issue. Check your SELinux status by getenforce. If it is Enabled, inspect the /var/log/audit/audit.log file.






            share|improve this answer












            On CentOS you have to deal with SELinux instead of AppArmor, if this might be an issue. Check your SELinux status by getenforce. If it is Enabled, inspect the /var/log/audit/audit.log file.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jun 15 '17 at 9:32









            Linuxfabrik

            362




            362












            • # getenforce - Disabled I also checked the audit files but nothing to see there, also if I tail the audit.log and create a print job. :(
              – Eldo.Ob
              Jun 15 '17 at 10:20


















            • # getenforce - Disabled I also checked the audit files but nothing to see there, also if I tail the audit.log and create a print job. :(
              – Eldo.Ob
              Jun 15 '17 at 10:20
















            # getenforce - Disabled I also checked the audit files but nothing to see there, also if I tail the audit.log and create a print job. :(
            – Eldo.Ob
            Jun 15 '17 at 10:20




            # getenforce - Disabled I also checked the audit files but nothing to see there, also if I tail the audit.log and create a print job. :(
            – Eldo.Ob
            Jun 15 '17 at 10:20












            up vote
            0
            down vote













            In CentOS there is another setting that causes the same symptoms. The post processing script runs as "nobody" user by default, so you must to add a line in the /etc/sudoers file to allow the script to run without prompting for a password:



            nobody ALL=(ALL) NOPASSWD:/yourpath/yourscript.sh






            share|improve this answer



























              up vote
              0
              down vote













              In CentOS there is another setting that causes the same symptoms. The post processing script runs as "nobody" user by default, so you must to add a line in the /etc/sudoers file to allow the script to run without prompting for a password:



              nobody ALL=(ALL) NOPASSWD:/yourpath/yourscript.sh






              share|improve this answer

























                up vote
                0
                down vote










                up vote
                0
                down vote









                In CentOS there is another setting that causes the same symptoms. The post processing script runs as "nobody" user by default, so you must to add a line in the /etc/sudoers file to allow the script to run without prompting for a password:



                nobody ALL=(ALL) NOPASSWD:/yourpath/yourscript.sh






                share|improve this answer














                In CentOS there is another setting that causes the same symptoms. The post processing script runs as "nobody" user by default, so you must to add a line in the /etc/sudoers file to allow the script to run without prompting for a password:



                nobody ALL=(ALL) NOPASSWD:/yourpath/yourscript.sh







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 7 at 17:13









                Rui F Ribeiro

                38.6k1479128




                38.6k1479128










                answered Dec 4 at 15:47









                Adriano Henrique Elingen

                1




                1






























                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f371273%2fcentos-7-cups-pdf-postprocessing-script-running-but-no-result%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

                    Morgemoulin

                    Scott Moir

                    Souastre