similar to: CentOS 7 as a Fibre Channel SAN Target

In waiting, I tried CentOS 8 which was an even bigger bust. I wiped that clean and tried again with Fedora 31. Same darn error "Could not create Target in configFS". Anyone?? Thank you, Steffan Cline steffan at hldns.com 602-793-0014 ?On 1/2/20, 2:00 AM, "CentOS on behalf of Steffan Cline via CentOS" <centos-bounces at centos.org on behalf of centos at centos.org>

Hi Steffan, I run my VMs on c7 using qemu-kvm + libvirt + virt-manager and the same on a slackware 14.2 without any problem. What error/problem do you receive? Il Ven 15 Nov 2019, 19:01 Steffan Cline <steffan at hldns.com> ha scritto: > I'm really curious how you were able to virtualize CentOS 8. > > What platform are you using? Xen, KVM or VMWare? PV or HVM? > > I

Permissions to the logs are fine. In /var/log/maillog I do see dovecot logging in there but nothing that indicates why there?s a failure. The one thing I thought of is if there?s too many connections but I am using a firewall that blocks excessive attempts but that?s fine. Netstat shows a bunch of CLOSE_WAIT though. I?ll try the debug level and see what I find. Thanks, Steffan Cline steffan at

I ran into something with a recent batch of updates on CentOS 7. It seems that possibly one of the kernel updates running dracut changed all of the volume groups in the grub.cfg file making the system unable to boot until I manually edited each line putting it back to the way it was originally. My volume group is called vg_h1 but it changed them all to the default ?centos?. Is there a config

I?ve started in the last day or so having issues where users get a timeout when connecting to dovecot. The iPhone interprets this as an auth issue but re-entering the password makes no change. Outlook will either just not connect to it at all or it gives an error to re-enter the password also with no change. This happens within an hour of a "service dovecot restart". I?m using

> On Jul 28, 2015, at 21:52 , Steffan Cline <steffan at hldns.com> wrote: > > Ok, I think I have come a little further. > > When dovecot stops accepting connections, I checked netstat and found this: > > [root at hosting1 ~]# netstat -an | grep 993 > tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN > tcp 0 0

https://github.com/st3fan/dovecot-xaps-daemon Works PERFECTLY. I use it on CentOS 6 and 7. Thanks, Steffan Cline steffan at hldns.com 602-793-0014 > On Jan 8, 2020, at 2:39 PM, infoomatic <infoomatic at gmx.at> wrote: > > ?I have no idea about that Mac proprietary stuff ... however, > https://doc.dovecot.org/configuration_manual/push_notification/ might be > a

I?m posting this here and will in a couple other places to see if anyone has any experience with this and knows what I can do. My setup is CentOS 6 with postfix, procmail and dovecot administered via Virtualmin. Postfix of course receives the email. Procmail uses it?s hooks to run the email through spam assassin and clamd. After than procmail hands it off to dovecot/deliver to drop it in the

I'm not the originator. I'm just trying to do some maintenance on the code to make it work for CentOS 7. I'll check out those two. Any ideas on how to check exactly what's sent via the socket? If the EOF is sent, I know to dig further into the daemon code. Thanks, Steffan Cline steffan at hldns.com 602-793-0014 > On Sep 7, 2017, at 11:43 PM, Aki Tuomi <aki.tuomi at

I?m working on an OS project from github. There are two parts: Dovecot plugin - https://github.com/st3fan/dovecot-xaps-plugin Daemon written in Go - https://github.com/st3fan/dovecot-xaps-daemon # dovecot --version 2.2.10 Both parts worked fine on CentOS 6 but I recently rebuilt them both for CentOS 7 and have run into some errors. The plugin sends a notification over a socket to

Steffan A. Cline wrote: > I?ve looked and looked and can?t seem to find anything which would > explain why grub.cfg would have been rewritten with a whole new volume > group name. > > Suggestions? > C6 or C7? In either case, have you looked in /etc/default/grub? mark

Hi all, I've several questions about C8. I'm using 8 on my personal NAS and works very well. I'm running several VMs with centos 8 and noticed something: 1) Why corosync, pacemaker and pcs are missing on C8? They are only available on rhel with payments( rhel ha addons)? 2) Why there is only Gnome as available DE? I use centos on my workstation and I'm a kde-plasma user. XFCE

I was reading thru the manual following the directions for installing Samba and for Mac OS X you are supposed to set the inetd.conf file and the services file. I did so but when ever I reboot the computer it never starts up the samba or swat. Anyone have any other ideas on what to do? Thanks Steffan --------------------------------------------------------------- T E L 6 0 2 . 5 7 9 . 4 2 3 0

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 28 Jul 2015, Steffan Cline wrote: > When dovecot stops accepting connections, I checked netstat and found this: > > [root at hosting1 ~]# netstat -an | grep 993 > tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN > tcp 0 0 65.39.x.x:993 184.101.x.x:36351 SYN_RECV

Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services). The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you

For quite some time I?ve been using FreeNAS to provide services as a NAS over ethernet and SAN over Fibre Channel to CentOS 7 servers each using their own export, not sharing the same one. It?s time for me to replace my hardware and I have a new R720XD that I?d like to use in the same capacity but configure CentOS 7 as a Fibre Channel target rather than use FreeNAS any further. I?m doing

In order to take advantages of Paolo's multi-queue virito-scsi, we need multi-target support in tcm_vhost first. Otherwise all the requests go to one queue and other queues are idle. This patch makes: 1. All the targets under the wwpn is seen and can be used by guest. 2. No need to pass the tpgt number in struct vhost_scsi_target to tcm_vhost.ko. Only wwpn is needed. 3. We can always pass

In order to take advantages of Paolo's multi-queue virito-scsi, we need multi-target support in tcm_vhost first. Otherwise all the requests go to one queue and other queues are idle. This patch makes: 1. All the targets under the wwpn is seen and can be used by guest. 2. No need to pass the tpgt number in struct vhost_scsi_target to tcm_vhost.ko. Only wwpn is needed. 3. We can always pass

Hi all I want to configure glusterfs to expose iSCSI target. I followed this artical https://pkalever.wordpress.com/2016/06/23/gluster-solution-for-non-shared-persistent-storage-in-docker-container/ but when I install tcmu-runner. It doesn't work. I setup on CentOS7 and installed tcmu-runner by rpm. When I run targetcli, it not show *user:glfs* and *user:gcow* */>* ls o- /

On Wed, Sep 13, 2017 at 1:03 PM, GiangCoi Mr <ltrgiang86 at gmail.com> wrote: > Hi all > Hi GiangCoi, The Good news is that now we have gluster-block [1] which will help you configure block storage using gluster very easy. gluster-block will take care of all the targetcli and tcmu-runner configuration for you, all you need as a pre-requisite is a gluster volume. And the sad part is