Re: [CentOS] Scope of classes in CFE 3.10.2 on CentOS 7 [SOLVED]
Am 10.07.2019 um 18:07 schrieb Meikel: Thanks in advance for any help or explanation of that behaviour. Hi folks, yesterday in the IRC I got an answer which explains everything for me, so from my point of view my question is answered and the problem is solved. In short with my words: The bundle scope_of_class_b1 is called one time for each entry in the slist, so it is called three times. The promisee of the "reports" type is "is_dir is SET" and even if the class "is_dir" is set in two of the three executions, the "report" is print out only once, because the promisee is the same, and a promise for the same promisee is only kept/repaired/executed only once in an agent run. To get the expected output the promisee of the "reports" has to be rewritten to become unique for each execution, i.e. adding $(server) like this: reports: is_dir:: "is_dir is SET"; is_dir:: "$(server): is_dir is SET"; !is_dir:: "$(server): is_dir is UNset"; I kept "is_dir is SET" to better show the difference. It gives the following result: # cf-agent -IK --file ./samples/scope_of_class.cf --bundlesequence scope_of_class info: Using command line specified bundlesequence R: is_dir is SET R: ws-1.example.com: is_dir is SET R: ws-2.example.com: is_dir is UNset R: webserver.example.com: is_dir is SET The output "is_dir is SET" is never shown more than once in one agent run, even if all three directories exist, but if the promisee becomes unique, i.e. "ws-1.example.com: is_dir is SET" vs. "webserver.example.com: is_dir is SET" then they're both print out. The problem is NOT, that the definition/evaluation of the class "is_dir" does not work as expected, it works as expected, but I didn't see it in the output, because my expectation of what to see was wrong. As I don't have skills in CFE my wording might be imprecise, I'm sorry, hopefully the idea became clear. Regards, Meikel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Scope of classes in CFE 3.10.2 on CentOS 7
Hi folks,
I have a question concerning scope of classes in CFEngine 3. I run CFE
3.10.2 on CentOS 7.4.
# cf-agent -V
CFEngine Core 3.10.2
# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
I'm logged in as root and located in current working dir /root. I have
the following file
# ll ./samples/scope_of_class.cf
-rwx--. 1 root root 720 10. Jul 16:33 ./samples/scope_of_class.cf
with content
BEGIN--
bundle agent scope_of_class()
{
vars:
any::
"web_servers" slist => {
"ws-1.example.com",
"ws-2.example.com",
"webserver.example.com",
};
methods:
any::
"scope_of_class_b1" usebundle => scope_of_class_b1(
$(scope_of_class.web_servers) );
}
bundle agent scope_of_class_b1( server )
{
classes:
any::
"is_dir"
expression => isdir( "/tmp/scope_of_class/$(server)" ),
scope => "bundle";
reports:
is_dir::
"is_dir is SET";
!is_dir::
"is_dir is UNset";
any::
"server = $(server)";
}
END
From my understanding the scope "bundle" is default for a class
definition inside a bundle of type agent, but I added the scope to be
sure. The definition of class is_dir should depend on directories
existing inside /tmp/scope_of_class. I have two subdirectories
# ls -1 /tmp/scope_of_class/
webserver.example.com
ws-1.example.com
but when I run CFE I do NOT get expected behaviour for the definition of
class is_dir:
# cf-agent -IK --file ./samples/scope_of_class.cf --bundlesequence
scope_of_class
info: Using command line specified bundlesequence
R: is_dir is SET
R: server = ws-1.example.com
R: is_dir is UNset
R: server = ws-2.example.com
R: server = webserver.example.com
When the bundle scope_of_class_b1 is processed for parameter
webserver.example.com I expect is_dir to bet set, but from the report it
seems not to be set.
If I change the slist definition to hold "webserver.example.com" as the
first entry, then the class is_dir is set correctly:
# grep slist ./samples/scope_of_class.cf -A 4
"web_servers" slist => {
"webserver.example.com",
"ws-1.example.com",
"ws-2.example.com",
};
# cf-agent -IK --file ./samples/scope_of_class.cf --bundlesequence
scope_of_class
info: Using command line specified bundlesequence
R: is_dir is SET
R: server = webserver.example.com
R: server = ws-1.example.com
R: is_dir is UNset
R: server = ws-2.example.com
It also works "correct" (or as expected by me) if "ws-2.example.com" is
first entry in the slist definition:
# grep slist ./samples/scope_of_class.cf -A 4
"web_servers" slist => {
"ws-2.example.com",
"ws-1.example.com",
"webserver.example.com",
};
# cf-agent -IK --file ./samples/scope_of_class.cf --bundlesequence
scope_of_class
info: Using command line specified bundlesequence
R: is_dir is UNset
R: server = ws-2.example.com
R: is_dir is SET
R: server = ws-1.example.com
R: server = webserver.example.com
I do not understand why the ordering inside slist influences how the
class is_dir will be defined later by CFE for each processing of
scope_of_class_b1.
Some background information: my aim is to create webserver vhost
configuration files where I have two variants, one with SSL
configuration and one without SSL configuration. Which one to configure
depends if the directory with the SSL certificate exists for a given
vhost or not. I'll replace the report promise type by a file promise
type, which should bring the correct vhost configuration file in place,
assumed that I understand how the scope of the class definition works.
Thanks in advance for any help or explanation of that behaviour.
Regards,
Meikel
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] Creating KVM-based VM with virt-manager and virt-install on C7
Hi folks, for learning purposes I create KVM-based VM with the virt-manager. Later I get rid of the VM and repeat the "process" again. When recreating the VM I always enter the same values into the wizard in virt-manager (i.e. I want to speicfy a given MAC). I'd like to "automate" this procedure, all of what I do in virt-manager for creating the new VM, I' d like to do it with a bash script using virt-install. I' wndering if it is possible to "record" the values when I enter them into virt-manager and extract those values for usage with virt-install? It's not clear to me when I enter a field in the wizard what is the corresponding parameter in virt-install. Regards, Meikel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem with definition of slist in CFEngine
Hi folks and Paul.
> Is there any chance that some elements of your info_list become larger
> than 4K size limit cfengine places on scalar variables?
Mayne the 4K limit ist not the problem here. I did some "shortcutting"
and added one more "undefined" variable aaa.bbb.ccc:
# cat ./info.cf
bundle agent info
{
vars:
any::
"info_list" slist => {
"aaa.bbb.ccc = $(aaa.bbb.ccc)",
"includes.dir ... = $(includes.dir)",
"sys.arch ... = $(sys.arch)",
"sys.bindir . = $(sys.bindir)",
"... BEGIN big shit ...",
#"sys.inet6 .. = $(sys.inet6)",
#"sys.interfaces_data = $(sys.interfaces_data)",
"... END big shit ..."
};
reports:
any::
"r1: $(info.info_list)";
"r2: sys.inet6 .. = $(sys.inet6)";
"r3: sys.interfaces_data = $(sys.interfaces_data)";
"r4: holleri di dudeldoe";
"r5: aaa.bbb.ccc = $(aaa.bbb.ccc)";
}
Variables aaa.bbb.ccc and includes.dir are not defined and do not cause
any problems:
# cf-agent -IK --file ./info.cf --bundlesequence info
info: Using command line specified bundlesequence
R: r1: aaa.bbb.ccc = $(aaa.bbb.ccc)
R: r1: includes.dir ... = $(includes.dir)
R: r1: sys.arch ... = x86_64
R: r1: sys.bindir . = /var/cfengine/bin
R: r1: ... BEGIN big shit ...
R: r1: ... END big shit ...
R: r4: holleri di dudeldoe
R: r5: aaa.bbb.ccc = $(aaa.bbb.ccc)
Adding sys.inet6 leads to the problem:
# cat ./info.cf
bundle agent info
{
vars:
any::
"info_list" slist => {
"aaa.bbb.ccc = $(aaa.bbb.ccc)",
"includes.dir ... = $(includes.dir)",
"sys.arch ... = $(sys.arch)",
"sys.bindir . = $(sys.bindir)",
"... BEGIN big shit ...",
"sys.inet6 .. = $(sys.inet6)",
#"sys.interfaces_data = $(sys.interfaces_data)",
"... END big shit ..."
};
reports:
any::
"r1: $(info.info_list)";
"r2: sys.inet6 .. = $(sys.inet6)";
"r3: sys.interfaces_data = $(sys.interfaces_data)";
"r4: holleri di dudeldoe";
"r5: aaa.bbb.ccc = $(aaa.bbb.ccc)";
}
]# cf-agent -IK --file ./info.cf --bundlesequence info
info: Using command line specified bundlesequence
R: r1: $(info.info_list)
R: r4: holleri di dudeldoe
R: r5: aaa.bbb.ccc .... = $(aaa.bbb.ccc)
Why is "r5:" shown but not "r2:" and "r3:"? Why isn't it possible to get
the reports "r2:" and "r3:"? There is something special with variables
sys.inet6 and sys.interfaces_data in my opinion.
Regards,
Meikel
Am 26.07.2018 um 22:01 schrieb Paul Heinlein:
On Thu, 26 Jul 2018, Meikel wrote:
Hey folks,
I have a problem with the definition of a variable of type slist in
CFEngine on
# uname -a ; cat /etc/redhat-release
Linux policyhub.example.com 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22
21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
CentOS Linux release 7.4.1708 (Core)
I'm not sure if its valid to ask CFEngine questions on this mailing
list, but as far as I'm running on CentOS I hope that it is okay.
I'm logged in as user
# id
uid=0(root) gid=0(root) Gruppen=0(root)
Kontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
and working on directory
# pwd
/var/cfengine/inputs
with software
# cf-agent -V
CFEngine Core 3.10.2
and the configuration file
# cat ./info.cf
bundle agent info
{
vars:
any::
"info_list" slist => {
"includes.dir ... = $(includes.dir)",
"sys.arch ... = $(sys.arch)",
"sys.bindir . = $(sys.bindir)",
"sys.cdate .. = $(sys.cdate)",
"sys.cf_promises = $(sys.cf_promises)",
"sys.cf_version . = $(sys.cf_version)",
"sys.cf_version_major ... = $(sys.cf_version_major)",
"sys.cf_version_minor ... = $(sys.cf_version_minor)",
"sys.cf_version_patch ... = $(sys.cf_version_patch)",
"sys.class .. = $(sys.class)",
"sys.cpus ... = $(sys.cpus)",
"sys.crontab = $(sys.crontab)",
Re: [CentOS] Problem with definition of slist in CFEngine
Hi folks and Alexander. > Any really good reason not to update since nearly 1 year? There are two reasons, but maybe they are not "good" reasons :-( First reason is that I'm an admin-beginner with low skills and missing practice. Second reason is that the system is brand new but from an 7.4-based DVD. It is installed via kickstart and CFEngine from an DVD I created based on 7.4. I'm bootstrapping that machine in an environment where it's hard for me to have services like DHCP (and TFTP and things like that) available, I'm not able to receive a kickstart file over network, so I have the network settings inside the kickstart file which is inside (my self-apckaged) ISO image. I'm too lazy to create an new kickstart DVD based on 7.5. I'm getting rid of the system and reinstalling-kickstarting-cfengining it every some days. It's for learning purposes. Maybe I'll create a 7.5 based ISO image and also add CFEngine rules to update the system (I don't have a strategie for the task of updating the system at the moment). Regards, Meikel Am 26.07.2018 um 18:58 schrieb Alexander Dalloz: Am 26.07.2018 um 17:11 schrieb Meikel: # uname -a ; cat /etc/redhat-release Linux policyhub.example.com 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.4.1708 (Core) Any really good reason not to update since nearly 1 year? Alexander ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Problem with definition of slist in CFEngine
= $(sys.winprogdir)
R: r1: sys.winprogdir86 ... = $(sys.winprogdir86)
R: r1: sys.winsysdir .. = $(sys.winsysdir)
R: r1: sys.workdir = /var/cfengine
R: r1: ... BEGIN big shit ...
R: r1: ... END big shit ...
R: r4: holleri di dudeldoe
"r2:" and "r3:" are missing, but thats not a problem for me. Now I
comment in one of those two lines, in this case th first one:
# cat ./info.cf
bundle agent info
{
vars:
any::
"info_list" slist => {
"includes.dir ... = $(includes.dir)",
"sys.arch ... = $(sys.arch)",
"sys.bindir . = $(sys.bindir)",
"sys.cdate .. = $(sys.cdate)",
"sys.cf_promises = $(sys.cf_promises)",
"sys.cf_version . = $(sys.cf_version)",
"sys.cf_version_major ... = $(sys.cf_version_major)",
"sys.cf_version_minor ... = $(sys.cf_version_minor)",
"sys.cf_version_patch ... = $(sys.cf_version_patch)",
"sys.class .. = $(sys.class)",
"sys.cpus ... = $(sys.cpus)",
"sys.crontab = $(sys.crontab)",
"sys.date ... = $(sys.date)",
"sys.doc_root ... = $(sys.doc_root)",
"sys.domain . = $(sys.domain)",
"sys.enterprise_version . = $(sys.enterprise_version)",
"sys.expires = $(sys.expires)",
"sys.exports = $(sys.exports)",
"sys.failsafe_policy_path ... = $(sys.failsafe_policy_path)",
"sys.flavor . = $(sys.flavor)",
"sys.flavour = $(sys.flavour)",
"sys.fqhost . = $(sys.fqhost)",
"sys.fstab .. = $(sys.fstab)",
"sys.hardware_addresses . = $(sys.hardware_addresses)",
"sys.host ... = $(sys.host)",
"sys.inet ... = $(sys.inet)",
"sys.inputdir ... = $(sys.inputdir)",
"sys.interface .. = $(sys.interface)",
"sys.interfaces . = $(sys.interfaces)",
"sys.interfaces_flags ... = $(sys.interfaces_flags)",
"sys.ip_addresses ... = $(sys.ip_addresses)",
"sys.ip2iface ... = $(sys.ip2iface)",
"sys.ipv4 ... = $(sys.ipv4)",
"sys.key_digest . = $(sys.key_digest)",
"sys.last_policy_update . = $(sys.last_policy_update)",
"sys.libdir . = $(sys.libdir)",
"sys.local_libdir ... = $(sys.local_libdir)",
"sys.logdir . = $(sys.logdir)",
"sys.license_owner .. = $(sys.license_owner)",
"sys.licenses_granted ... = $(sys.licenses_granted)",
"sys.long_arch .. = $(sys.long_arch)",
"sys.maildir = $(sys.maildir)",
"sys.masterdir .. = $(sys.masterdir)",
"sys.os . = $(sys.os)",
"sys.ostype . = $(sys.ostype)",
"sys.piddir . = $(sys.piddir)",
"sys.policy_hub . = $(sys.policy_hub)",
"sys.policy_hub_port = $(sys.policy_hub_port)",
"sys.release = $(sys.release)",
"sys.resolv . = $(sys.resolv)",
"sys.statedir ... = $(sys.statedir)",
"sys.sysday . = $(sys.sysday)",
"sys.systime = $(sys.systime)",
"sys.update_policy_path . = $(sys.update_policy_path)",
"sys.uptime . = $(sys.uptime)",
"sys.user_data .. = $(sys.user_data)",
"sys.uqhost . = $(sys.uqhost)",
"sys.version = $(sys.version)",
"sys.windir . = $(sys.windir)",
"sys.winprogdir . = $(sys.winprogdir)",
"sys.winprogdir86 ... = $(sys.winprogdir86)",
"sys.winsysdir .. = $(sys.winsysdir)",
"sys.workdir = $(sys.workdir)",
"... BEGIN big shit ...",
"sys.inet6 .. = $(sys.inet6)",
#"sys.interfaces_data = $(sys.interfaces_data)",
"... END big shit ...",
};
reports:
any::
"r1: $(info.info_list)";
"r2: sys.inet6 .. = $(sys.inet6)";
"r3: sys.interfaces_data = $(sys.interfaces_data)";
"r4: holleri di dudeldoe";
}
I "run" again with that configuration file and in report "r1:" I can see
that now the stringlist/slist "info_list" seems to be undefined and
report "r1:" is empty and reports "r2:" and "r3:" are still missing:
# cf-agent -IK --file ./info.cf --bundlesequence info
info: Using command line specified bundlesequence
R: r1: $(info.info_list)
R: r4: holleri di dudeldoe
My problem ist NOT that the reports "r2:" and "r3:" are not printed, my
problem ist, that in some cases the slist is undefined. I'm using that
slist to collect some system info and then printing out the report and
it would NOT be a problem if some system informations were missing but
it IS a problem that in some cases the whole slist becomes undefined and
in that situation I receive a completly empty report "r1: ".
I would like to understand what circumstances lead to the slist be
undefined and how I can prevent this.
Thanks in advance.
Regards, Meikel
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Which is better? Microsoft Exchange 2016 or Linux-based SMTP Servers?
[...] People want their phone to remind them of their appointments [...] It's a generalization. Not valid for all people. Maybe SOME people want their phone to remind them of their appointsments. My appointments are synchronized from owncloud to Thunderbird and to many (LineageOS-based) smartphones and tablets and >>I<< do NOT want to be reminded on the smartphones and tablets, but ONLY on Thunderbird desktop client. Regards, Meikel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Network configuration issue with second public ip on CentOS 6
Hi folks, I have a server at Soyoustart.com (which is a brand of OVH). I run CentOS 6.7 and have problems with network configuration. I want to add a second public ip (failover ip) to the server and did follow the instructions in the CentOS-section of http://hilfe.ovh.de/AdministrationIpAliasHinzufuegen After executing the required steps I'm not able to reach the host via the second ip from an external host. I tried it with ping and with ssh commands. Here the content of the config files (I anonymized the server ip with xx.xx.xx.xx and the failover ip with yy.yy.yy.yy): $ cat /etc/sysconfig/network NETWORKING=yes HOSTNAME= NOZEROCONF=true GATEWAY=xx.xx.xx.254 $ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static IPADDR=xx.xx.xx.xx NETMASK=255.255.255.0 ONBOOT=yes GATEWAY=xx.xx.xx.254 $ cat /etc/sysconfig/network-scripts/ifcfg-eth0:0 DEVICE=eth0:0 BOOTPROTO=static IPADDR=yy.yy.yy.yy NETMASK=255.255.255.255 ONBOOT=yes When I restart the network I get a message (two times) saying "RTNETLINK answers: Operation not supported". $ service network restart Schnittstelle eth0 beenden:[ OK ] Loopback-Schnittstelle beenden:[ OK ] Loopback-Schnittstelle hochfahren: [ OK ] Schnittstelle eth0 hochfahren: Determining if ip address xx.xx.xx.xx is already in use for device eth0... RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported [ OK ] I can see two interfaces eth0 and eth0:0 $ LANG="" ifconfig eth0 Link encap:Ethernet HWaddr ..:..:..:..:..:.. inet addr:xx.xx.xx.xx Bcast:xx.xx.xx.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11122 errors:0 dropped:0 overruns:0 frame:0 TX packets:14371 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1362900 (1.2 MiB) TX bytes:3462327 (3.3 MiB) Interrupt:20 Memory:fe50-fe52 eth0:0Link encap:Ethernet HWaddr ..:..:..:..:..:.. inet addr:yy.yy.yy.yy Bcast:yy.yy.yy.yy Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:20 Memory:fe50-fe52 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:3096 errors:0 dropped:0 overruns:0 frame:0 TX packets:3096 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:274948 (268.5 KiB) TX bytes:274948 (268.5 KiB) I'm able to reach the host from another host (outside OVH network) via xx.xx.xx.xx (I use ping and ssh), but not via yy.yy.yy.yy. Just to be sure that there isn't an issue with the firewall I did "service iptables stop" and ran the "ping" and "ssh" commands again with the same result. For ip xx.xx.xx.xx it works, but not for yy.yy.yy.yy. Not sure if this is important, just in case it matters, some additional information: IPv6 is disabled by kernel parameter "ipv6.disable=1" in /etc/grub.conf The two mac addresses I see for eth0 and eth0:0 with the "ifconfig" command are the same. In the OVH/Soyoustart.com GUI I created a virtual mac for the failover ip, I'm not sure if that virtual mac should come into play somewhere? $ uname -a Linux 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ LANG="" route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface xx.xx.xx.0 * 255.255.255.0 U 0 00 eth0 default vss-gw-6k.fr.eu 0.0.0.0 UG0 00 eth0 Why is yy.yy.yy.yy not reachable from outside? What am I doing wrong or what can I do to narrow down the problem? Regards, Meikel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210
Am 26.09.2015 um 14:22 schrieb Akemi Yagi: On Sat, Sep 26, 2015 at 3:08 AM, Meikel <mei...@fn.de> wrote: scanner by a CanoScan LiDE 210. Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.21 I have no idea what I can do now. It is not clear to me if sane-backends package really includes the required genesys 1.0-63 version. You need sane-backends 1.0.22 or later to have genesys 1.0-63. There are a few ways to install a newer version of sane-backends on EL6. One is to rebuild a src.rpm from Fedora. The other is to use the linuxtech-backports repo [1]. I have even built it from a tarball but this should not be necessary. As I have only very basic skills with yum command I had problems with the same packages (i.e. sane-backends, sane-backends-libs, sane-backends-libs-gphoto) available in two repos. Then I ended in using yum to remove everything concerning xsane/sane (including hp sane packages), then downloading from linuxtech and running "rpm -U ..." and then with yum I again installed xsane. Now I'm able to see the CanoScan LiDE 210 in xsane and it seems to work, at least I'm able to scan single page into a PDF file. And the command line says # LANG="" yum info sane-backends ... Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.22 Release : 3.1.el6 Size: 4.5 M Repo: installed ... # scanimage -L device `genesys:libusb:003:005' is a Canon LiDE 210 flatbed scanner ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210 [SOLVED]
Am 30.09.2015 um 08:30 schrieb Meikel: Am 26.09.2015 um 14:22 schrieb Akemi Yagi: On Sat, Sep 26, 2015 at 3:08 AM, Meikel <mei...@fn.de> wrote: scanner by a CanoScan LiDE 210. Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.21 I have no idea what I can do now. It is not clear to me if sane-backends package really includes the required genesys 1.0-63 version. You need sane-backends 1.0.22 or later to have genesys 1.0-63. There are a few ways to install a newer version of sane-backends on EL6. One is to rebuild a src.rpm from Fedora. The other is to use the linuxtech-backports repo [1]. I have even built it from a tarball but this should not be necessary. As I have only very basic skills with yum command I had problems with the same packages (i.e. sane-backends, sane-backends-libs, sane-backends-libs-gphoto) available in two repos. Then I ended in using yum to remove everything concerning xsane/sane (including hp sane packages), then downloading from linuxtech and running "rpm -U ..." and then with yum I again installed xsane. Now I'm able to see the CanoScan LiDE 210 in xsane and it seems to work, at least I'm able to scan single page into a PDF file. And the command line says # LANG="" yum info sane-backends ... Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.22 Release : 3.1.el6 Size: 4.5 M Repo: installed ... # scanimage -L device `genesys:libusb:003:005' is a Canon LiDE 210 flatbed scanner ... which means SOLVED !!! Thanks very much. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 6 - Support for CanoScan LiDE 210
Hi folks, for some time I used a HP 2840 AiO device, connected via LAN, to scan documents. As scanning application I use xsane. I want to replace that HP scanner by a CanoScan LiDE 210. # LANG="" yum info libsane-hpaio ... Installed Packages Name: libsane-hpaio Arch: x86_64 Version : 3.14.6 Release : 3.el6 Size: 148 k Repo: installed From repo : base Summary : SANE driver for scanners in HP's multi-function devices URL : http://hplip.sourceforge.net/ License : GPLv2+ Description : SANE driver for scanners in HP's multi-function devices (from HPOJ). Now I connected CanoScan LiDE 210 Scanner via USB cable to my CentOS 6 workstation. # dmesg | tail --lines=15 ... usb 3-1: new high speed USB device number 8 using xhci_hcd usb 3-1: New USB device found, idVendor=04a9, idProduct=190a usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: CanoScan usb 3-1: Manufacturer: Canon usb 3-1: configuration #1 chosen from 1 choice ... After opening xsane it seems to be connected to the HP Scanner. I can not find any options for choosing another scanner device. From http://www.sane-project.org/sane-mfgs.html I can see that CanoScan LiDE 210 is supported by genesys 1.0-63. From my understanding on CentOS the genesys backend is included in sane-backends: # LANG="" yum info sane-backends ... Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.21 Release : 3.el6 Size: 4.4 M Repo: installed From repo : anaconda-CentOS-201410241409.x86_64 Summary : Scanner access software URL : http://www.sane-project.org License : GPLv2+ and GPLv2+ with exceptions and Public Domain Description : Scanner Access Now Easy (SANE) is a universal scanner interface. The : SANE application programming interface (API) provides standardized : access to any raster image scanner hardware (flatbed scanner, : hand-held scanner, video and still cameras, frame-grabbers, etc.). The sane-backends is installed, but I can not "see" the scanner: # scanimage -L device `hpaio:/net/HP_Color_LaserJet_2840?zc=NPI9AC264' is a Hewlett-Packard HP_Color_LaserJet_2840 all-in-one I have no idea what I can do now. It is not clear to me if sane-backends package really includes the required genesys 1.0-63 version. Any help to make the new scanner work is appreciated. Regards, Meikel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 - Support for CanoScan LiDE 210
Am 26.09.2015 um 13:11 schrieb Leon Fauster: Am 26.09.2015 um 12:08 schrieb Meikel <mei...@fn.de>: Hi folks, for some time I used a HP 2840 AiO device, connected via LAN, to scan documents. As scanning application I use xsane. I want to replace that HP scanner by a CanoScan LiDE 210. # LANG="" yum info libsane-hpaio ... Installed Packages Name: libsane-hpaio Arch: x86_64 Version : 3.14.6 Release : 3.el6 Size: 148 k Repo: installed From repo : base Summary : SANE driver for scanners in HP's multi-function devices URL : http://hplip.sourceforge.net/ License : GPLv2+ Description : SANE driver for scanners in HP's multi-function devices (from HPOJ). Now I connected CanoScan LiDE 210 Scanner via USB cable to my CentOS 6 workstation. # dmesg | tail --lines=15 ... usb 3-1: new high speed USB device number 8 using xhci_hcd usb 3-1: New USB device found, idVendor=04a9, idProduct=190a usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-1: Product: CanoScan usb 3-1: Manufacturer: Canon usb 3-1: configuration #1 chosen from 1 choice ... After opening xsane it seems to be connected to the HP Scanner. I can not find any options for choosing another scanner device. From http://www.sane-project.org/sane-mfgs.html I can see that CanoScan LiDE 210 is supported by genesys 1.0-63. From my understanding on CentOS the genesys backend is included in sane-backends: # LANG="" yum info sane-backends ... Installed Packages Name: sane-backends Arch: x86_64 Version : 1.0.21 Release : 3.el6 Size: 4.4 M Repo: installed From repo : anaconda-CentOS-201410241409.x86_64 Summary : Scanner access software URL : http://www.sane-project.org License : GPLv2+ and GPLv2+ with exceptions and Public Domain Description : Scanner Access Now Easy (SANE) is a universal scanner interface. The : SANE application programming interface (API) provides standardized : access to any raster image scanner hardware (flatbed scanner, : hand-held scanner, video and still cameras, frame-grabbers, etc.). The sane-backends is installed, but I can not "see" the scanner: # scanimage -L device `hpaio:/net/HP_Color_LaserJet_2840?zc=NPI9AC264' is a Hewlett-Packard HP_Color_LaserJet_2840 all-in-one I have no idea what I can do now. It is not clear to me if sane-backends package really includes the required genesys 1.0-63 version. Any help to make the new scanner work is appreciated. is it enabled in dll.conf ? As far as I can see, it is enabled there: # grep genesys /etc/sane.d/dll.conf genesys ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] How to search in mailing list
Hi folks, I want to search the CentOS mailing list(s) for how to upgrade from PHP 5.3.3 to 5.4 (or higher) on CentOS 6.7. From "CentOS Mailing Lists and Posting Guidelines" I can see "All public mailing lists are archived and those archives are searchable - there's a search box in the upper left corner on each of the lists listinfo page." Then after opening http://lists.centos.org/mailman/listinfo/centos (which from my understanding is the "listinfo page") I don't see any search functionality. Just to be sure I followed to the CentOS archieves at http://lists.centos.org/pipermail/centos/ which as well doesn't contain any search functionality. Can please someone point me to where I can search the CentOS mailing list? Regards, Meikel ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Samba-based Home-Directory
Am 08.07.2015 um 08:38 schrieb Meikel: I think the next step for me to do is to check the ethernet cable(s). Yes, it was a problem with the cable between the patch field and the outlet, I temporarily moved to another outlet and it works. And i double checked the defect cable with other devices and can see the same problems. I still get the message Jul 21 08:06:04 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready but in the same second I then can see Jul 21 08:06:04 meikel-pc kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Jul 21 08:06:04 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready and as I can see the link speed is 1000 Mbps now. The other problem Could not update ICEauthority file /home/meikel/.ICEauthority has gone, so probably due to cabling problem the network became ready much to late and autofs wasn't able to mount /home when logging in. So now everything is fine. Regards, Meikel ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Samba-based Home-Directory [SOLVED]
So the directory /home/meikel is definitely there. Can someone explain the error message No directory /home/meikel! and give any hints about possible problem causes? How can it say that the directory isn't here but I can see all the data? Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready There were two problems. Solution for the first: setsebool -P use_samba_home_dirs 1 Solution for the second: The ethernet cable was defect, I had to replace it. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Samba-based Home-Directory
Am 07.07.2015 um 13:49 schrieb Steven Tardy: http://www.dlink.com/-/media/Business_Products/DGS/DGS%201210%2048/Manual/DGS_1210_Series_Manual_v4_00_EN.pdf What are the current settings on the switch for: Loopback Detection page 35 STP Global Settings page 38 STP Port Settings page 39 Under STP Global the forward delay defaults to 15 seconds... The same delay you're seeing. Loopback Detection Settings = Disabled STP Global Settings = Disabled STP Port Settings = ... it seams to be disabled, I can't edit any of the fields, but State is Enabled ... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Samba-based Home-Directory
Am 07.07.2015 um 07:13 schrieb Gordon Messmer: Google-fu also turns up a suggestion that the switch doesn't negotiate properly in some cases, and that the problem can be resolved by disabling power saving mode on the switch, in its management interface. There is really a Power Saving option which was turned on. I disabled it, but the problem remains. I think the next step for me to do is to check the ethernet cable(s). ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Samba-based Home-Directory
Am 05.07.2015 um 21:13 schrieb Steven Tardy: What is the upstream switch? If it is a Cisco switch does the configuration have `spanning-tree portfast` enabled? http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/10553-12.html ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos It's a D-Link DGS-1210-16 Switch. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Samba-based Home-Directory
Am 05.07.2015 um 20:52 schrieb Gordon Messmer: On 07/05/2015 07:57 AM, Meikel wrote: Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready It takes 15 seconds between the two messages until it becomes ready. I have no idea why it first says that the link is not ready. It's probably autonegotiation of link speed. I'm not sure why it'd take that long. I'd think the most likely explanation would be a bad cable. Could also be a flaky port on the switch, or a flaky Ethernet card. What brand is the local interface? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos I'll check the cable (not clear how I can do that, probably using another cable and connecting to another outlet). I think the local interface is directly integrated into the Intel Desktop Board DH87RL. dmesg | grep eth e1000e :00:19.0: eth0: registered PHC clock e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:22:4d:b0:e0:e1 e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network Connection e1000e :00:19.0: eth0: MAC: 11, PHY: 12, PBA No: FF-0FF ADDRCONF(NETDEV_UP): eth0: link is not ready e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None e1000e :00:19.0: eth0: 10/100 speed: disabling TSO ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present lspci | grep Ether 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) It says that it has a speed of 10/100, but I definitely expect 1000 Mbps! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problems with Samba-based Home-Directory
Am 02.07.2015 um 20:16 schrieb Gordon Messmer: Have you yet: setsebool -P use_samba_home_dirs 1 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos No, I didn't set it. Now I've set it and when logging into text console I no longer have the problem with the home directory. That's fine now. Thanks a lot! But the other problem remains, that very soon after startup I can't log into the GUI. I think the remaining problem doesn't has to do something with Samba/Autofs. It looks as if the network becomes ready very late (after autofs started), which perhaps would explain my problem. In the /var/log/boot.log I see: ... Schnittstelle eth0 hochfahren: IP-Informationen für eth0 werden bestimmt ... fehlgeschlagen; keine Verbindung vorhanden. Kabel prüfen? FEHLGESCHLAGEN ... Netzwerkparameter einstellen ... OK NetworkManager-Daemon starten: OK Loading autofs4: OK automount starten: OK In /var/log/messages I see: Jul 5 16:36:08 meikel-pc kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 5 16:36:23 meikel-pc kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready It takes 15 seconds between the two messages until it becomes ready. I have no idea why it first says that the link is not ready. Any ideas? Regards, Meikel ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Problems with Samba-based Home-Directory
Hi folks,
I'm running CentOS 6.6 on my workstation. There I have a user meikel,
and its home directory /home/meikel ist stored on a samba share on a
server which also runs CentOS 6.6.
In the very beginning I added the mount options for that home directory
into the /etc/fstab file which led to some problems, so I set up autofs
for mounting the home directory.
The autofs seems to work for /home/meikel, but sometimes when I login at
the GUI, I get error messages which look a little as if the home dir
isn't available, I then also don't get my desktop background image. The
two error dialogs which I get in that situation show the following messages:
Could not update ICEauthority file /home/meikel/.ICEauthority
and
Es gibt ein Problem mit dem Konfigurationsserver.
(/usr/libexec/gconf-sanity-check-2 beendet mit Status 256)
Sorry for the german, it's not clear to me how to get it in english.
It's something like There's a problem with configuration server.
(/usr/libexec/gconf-sanity-check-2 terminated with exit-code 256)
To do some analysis I did the following:
- Restart workstation, wait until login screen appears
- use CTRL-ALT-F2 to go to a text console
- log in as root
- mount -- it seems that /home/meikel isn't mounted (and this is what I
expect)
- ll /home/meikel/ -- it's fine, I can see alls the files and
subdirectories
- ll /home/meikel/Dokumente/ -- it's also fine
- df -h /home/meikel -- now the mount is there
- mount | grep meikel -- yes, the mount is there
- use CTRL-ALT-F3 to go to another text console
- log in as user meikel -- I get an error saying No directory
/home/meikel!, but I'm logged in
- pwd -- it shows the root dir /
- id -- it shows uid=500(meikel) gid=500(meikel)
- ll -d /home/meikel -- drwx-- meikel:meikel
- echo ${HOME} -- shows /home/meikel
So the directory /home/meikel is definitely there. Can someone explain
the error message No directory /home/meikel! and give any hints about
possible problem causes? How can it say that the directory isn't here
but I can see all the data?
Regards,
Meikel
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] Yum update changes inode of file
Hi folks, on CentOS 6.5 I run tripwire software which verifies data integrity. My system is automatically updated by yum (as far as I understand the /etc/cron.daily/0yum.cron is responsible for the regular system updates). After a system update I'm then notified by tripwire about the changes on the file system. By browsing those tripwire reports I found that there are files which did not change at all (i.e. the MD5 hash is the same as before) but the inode changed. I do not understand what yum did to the file that resulted in an inode change, especially I'm wondering how the inode can change although there was no modification on the file at all. Thanks in advance for any clarification. Find below an excerpt from the tripwire log (for /etc/nsswitch.conf) which shows that only inode changed. Regards, Meikel Excerpt from tripwire report: Modified object name: /etc/nsswitch.conf Property:ExpectedObserved ---- --- Object Type Regular FileRegular File Device Number64770 64770 * Inode Number 393292 393686 Mode -rw-r--r-- -rw-r--r-- Num Links1 1 UID root (0)root (0) GID root (0)root (0) Size 16881688 Modify Time Tue 04 May 2010 09:22:21 PM CEST Tue 04 May 2010 09:22:21 PM CEST Blocks 8 8 CRC32DjDI7W DjDI7W MD5 ANYAnN/RJkbSUehjA7wMSM ANYAnN/RJkbSUehjA7wMSM ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 6.4 installation fails with message No usable disks have been found
Hi folks, I inherited a very old computer (I guess about 8 years old) which I'd like to use for some training on CentOS. I downloaded images for CentOS 6.4 i386 (DVD 1 and 2) and burned them onto discs. After inserting DVD 1 into drive and booting, on the Welcome to CentOS 6.4! screen I select Install or upgrade an existing system. I then skip the media test and start the installation. Then I get a graphical installer where I choose english language and U.S. international keyboard layout. Then I'm questioned about What type of devices will your installation involve? where I select Basic Storage Devices and then proceed. I get a dialog Examining devices with the message Examining storage devices. After a short while a dialog No disks found appears displaying the message No usable disks have been found. I then go back and choose Specialized Storage Devices but I then get the same result (no devices are found). Just to be sure that there are disks available and hardware works I installed a current Debian which works fine. From the BIOS and from Debian shell command dmesg | grep -i ata I see that there are two Maxtor 6Y120L0 installed. Find output of dmsg below that email. Is it possible and what steps are necessary to install CentOS 6.4 on that Maxtor 6Y120L0 hard disks? Regards, Meikel --- Output of dmesg | grep -i ata [1.690559] pata_via :00:11.1: version 0.3.4 [1.690591] pata_via :00:11.1: can't derive routing for PCI INT A [1.693019] scsi0 : pata_via [1.693396] scsi1 : pata_via [1.694434] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xa800 irq 14 [1.694442] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xa808 irq 15 [1.864541] ata1.00: ATA-7: Maxtor 6Y120L0, YAR41BW0, max UDMA/133 [1.864549] ata1.00: 240121728 sectors, multi 16: LBA [1.864737] ata1.01: ATA-7: Maxtor 6Y120L0, YAR41BW0, max UDMA/133 [1.864744] ata1.01: 240121728 sectors, multi 16: LBA [1.880389] ata1.00: configured for UDMA/133 [1.896439] ata1.01: configured for UDMA/133 [1.896738] scsi 0:0:0:0: Direct-Access ATA Maxtor 6Y120L0 YAR4 PQ: 0 ANSI: 5 [1.897477] scsi 0:0:1:0: Direct-Access ATA Maxtor 6Y120L0 YAR4 PQ: 0 ANSI: 5 [2.068361] ata2.00: ATAPI: HL-DT-ST DVDRAM GSA-4167B, DL11, max UDMA/33 [2.068375] ata2.01: ATAPI: CD-956E/AKV, A99, max UDMA/33 [2.084228] ata2.00: configured for UDMA/33 [2.100283] ata2.01: configured for UDMA/33 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
