December 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] running asterisk
by Per Jessen 15 Dec '16

15 Dec '16

Carlos E. R. wrote: > On 2016-12-13 18:27, Per Jessen wrote: >> Carlos E. R. wrote: > >>>> Carlos E. R. wrote: >>> >>> >>>> That was my thought too - you could run asterisk internally, >>>> but it's a bit of big gun for this. >>> >>> And it is a target for attacks :-( >> >> Everything is a target, but it's not a big deal - you get a lot of >> people trying to gain access to a SIP account, but it is so easily >> blocked. I've been running asterisk as our telephone system for >> at least 8 years. For Roger's purpose though, it's far too much >> effort to set up, I would say. > > I might play again with asterisk, I would like to install it again. > But I only played on a LAN. Facing outside I think it is bombarded by > script kiddies. Yes it will be eventually. There isn't really any reason for you to have it open externally, unless you want/need - IAX connections (can be useful for some public gateways) external SIP provider (for real numbers for instance). external devices The script kiddies (and more serious people) will be banging down your port 5060, but that's taken care with a good sip config and some rate control. Maybe fail2ban. When I was setting up offices for my company about ten years ago, at first I bought a 2nd hand telephone exchange (PABX) including telephones. I quickly found out that everything you needed was tied into software licenses and extra cost, so after spending Christmas setting up asterisk, I sold it all again and never looked back. -- Per Jessen, Zürich (0.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 17

[opensuse] Drobo box experience
by Per Jessen 15 Dec '16

15 Dec '16

Greg Freemyer wrote: > On Tue, Dec 6, 2016 at 2:46 AM, Per Jessen <per(a)computer.org> wrote: >> Greg Freemyer wrote: >> >>> Got my Drobo today. So far I'm not impressed. >>> >>> Pros: >>> >>> I plugged in 8 1TB drives and it saw them and let me thin provision >>> a 16TB volume. >> >> That sounds like a major pro (or con) - 16Tb with only 8Tb space :-) >> I guess it automagically dealt with RAID levels and such? > > Thin provisioning works like that, and yes as I think about it, it is > a major pro. Okay, I thought it was a typo - with LVM, thin provisioning just means the space isn't all allocated, but I doubt if you can allocate a volume that is bigger than what is available in a PV. Well, it has never occurred to me to try it :-) I usually allocate what I need, then extend later on when needed. > The user manual does recommend that this particular Drobo only provide > iSCSI volumes to one host. It's not a mandate, but it is how the best > performance is achieved. Normally the main advantage of SCSI is the concurrency, but your Drobo is hardly a full-blooded SAN box. Maybe it's only got one processor or all the drives are on a single SATA bus. Mind you, with the usage pattern you have in mind, performance isn't critical, right? > Newer / higher performing Drobo's can support multiple hosts. And the > FS versions include a true fileserving capability. As in NFS? Yes, these days on GigE and with NFSv4 there's little gained with iSCSI over NFS. You can boot from iSCSI, which is cool, but NFS is quite straight forward. Setting up iSCSI with authentication, redundancy and multi-pathing can be a little daunting. >>> I pulled out one of the 1TB drives and popped in my 10TB drive. It >>> recognized it and rebuilt my volume. The rebuild only took a minute >>> or two, but I only have 6GB of data on the volume and it is thin >>> provisioned, so not much data to move around. >> >> Resync'ing 16Gb on plain ol' spinning SATA drives will take a while >> longer. If the time-to-resync on the Drobo varies with the amount of >> data, the logic is at a different level. Interesting, I think. > > I think that is part of the thin provisioning. As a volume gets > filled, more free data blocks are provisioned. When a drive fails, > only the provisioned data blocks have to be rearranged. I can see a major advantage in reduced recovery times when only data-in-use has to be resynched. Of course, when a drive is 80% full, that is still only 20% saved, but even so. > I put 1.5TB of data on the unit overnight. This morning I pulled one > of the 1TB drives to see what it will do. SInce I have plenty of > spare space on the spindles, A new raid arrangement is being laid > down. At the end I will once again be able to handle a drive failure. > An hour later, it is still in the rebuild process and the estimate is > 12 more hours to complete. Wow. Surely that's not good - that's too long to be running degraded. I must have misunderstood - you said only allocated data needs to be resynched/re-arranged? > This Drobo only has 1 1-Gbit port. I'm seeing about 30 MB/sec > speeds., but I'm sharing a single NIC on the server, so that's > 30MB/sec incoming to the server and 30MB/sec outgoing to the Drobo. > 60 MB/sec total. > Not too bad for a 1-Gbit port. I'm assuming that > single port of the server is the bottleneck. You ought to get more out of it, I would say. Twice as much. Just downloading an ISO from an openSUSE mirror site, I can drive our uplink to 50Mb/s, doing an scp copy between two non-optimized local systems I get 80MB/s. Doing it full-duplex (both ways concurrently), I can easily run it up to 65+65Mb/s. With iSCSI it ought to exceed that (no encryption for instance). There are other limiting factors, depending on what's in the Drobo - SATA bus speed, and PCI/e ditto. Maybe also your switch? > As I said for peak performance I need to establish a dedicated storage > LAN. which doesn't carry any front office traffic. That will take a > week or so to setup since I need to get a few miscellaneous parts. I don't think your LAN is the limiting factor. -- Per Jessen, Zürich (-0.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 37

[opensuse] using "surveillance"' disks in a raid set
by Greg Freemyer 14 Dec '16

14 Dec '16

On Wed, Dec 14, 2016 at 2:22 AM, Per Jessen <per(a)computer.org> wrote: > Greg Freemyer wrote: > >> FYI: >> I bought a "surveillance" HDD this last time (Seagate Skyhawk). The >> first was a Seagate Barracuda. The surveillance drive was almost 20% >> cheaper. >> >> > http://www.seagate.com/www-content/product-content/skyhawk/files/skyhawk-ds… >> >> The surveillance drive claims to be pretty robust and that is what I >> care about more than performance for this situation. I can't help but >> wonder if they aren't the same drive with different labels and >> warranties attached. > > I expect they're 5400/5900rpm, which means bigger margins everywhere. http://www.seagate.com/www-content/product-content/skyhawk/files/skyhawk-ds… http://www.seagate.com/www-content/product-content/barracuda-fam/barracuda-… The Skyhawk spec appears intentionally to miss key specs. I suspect they don't want people to do what I'm doing and use it in a general RAID set. RPM drives max throughput in a simple linear manner. For the Barracuda Pro (7200 rpm): max throughput 220 MB/sec For the Skyhawk: max throughput 210 MB/sec If they are the same drive, they are under reporting the max throughput on the Skyhawk, but only 5%. It is not slow enough to be a 5400 rpm drive IMO. Carlos said he only expects to get 50,000 power on hrs out of a drive. The Skyhawk is said to be designed for always on operation and gives a million hours MTBF. That's the biggest MBTF I've ever seen and is a lot of years (over 100?) The Barracuda Pro has a 5 year warranty, but the spec doesn't show MTBF! They are playing games with these 2 specs to keep you from doing a good comparison. > They also intended for streaming to, not reading with random access. Marketing spin? It says it supports up to 64 cameras. That's likely to involve a lot of seeking. > 3-year warranty only. A way to cut cost for cost conscious buyers? > I feel certain they're coming off a different > assembly line. I'll power off the Drobo today and see if they look different as far as the exposed parts go. > I replace SATA drives regularly - we have a lot - the WD RE4 and the > older IBM/Hitachi Ultrastar are the best, anything consumer-oriented (3 > year warranty) will die almost exactly when the warranty expires. The WD green drives worked horribly in my normal use case. I too like the Ultrastar. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 13

Re: [opensuse] Re: multi disk failures
by Greg Freemyer 14 Dec '16

14 Dec '16

On Wed, Dec 14, 2016 at 9:12 AM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > On Wed, Dec 14, 2016 at 8:50 AM, Per Jessen <per(a)computer.org> wrote: >> Greg Freemyer wrote: >> >>> On Wed, Dec 14, 2016 at 8:07 AM, Per Jessen <per(a)computer.org> wrote: >>>> jdd wrote: >>>> >>>>> Le 14/12/2016 à 11:40, Per Jessen a écrit : >>>>>> jdd wrote: >>>>> >>>>>>> my main concern on raid is unused data control, that is >>>>>>> verification of the integrity of unused data on disk (to prevent >>>>>>> unexpected multi disk failure). >>>>>> >>>>>> Huh? You mean check unused data >>>>> >>>>> data >>>>> >>>>> or unused space? I don't see what you >>>>>> would gain and I am not aware of any enterprise class hardware that >>>>>> will do it. Usually SMART (and other vendor-specific diagnostics) >>>>>> tests are run regularly, that's about it. If you cannot rely on >>>>>> your data being written accurately to your disk, all bets are off. >>>>>> >>>>>> >>>>> it's certainly a problem. I read recently a discussion about it (but >>>>> don't remember the exect name): >>>>> >>>>> loook at this >>>>> >>>>>http://sysadmin1138.net/mt/blog/2012/12/how-multi-disk-failures-happen.shtml >>>> >>>> Yes, multi disk failures definitely do happen, the risk increases >>>> with the drive size. That's why we use DRBD mirror copies, hot >>>> spares and RAID6, staged drive purchases, and make sure each array >>>> has a good mix of different drive ages. >>> >>> Now you just need to mix in some surveillance disks :) >> >> Haha - given that they intended for 100% duty cycle, I do see some >> interesting use cases. Problems I see - apparently they don't support >> hot-swap, and the 3-year warranty. Pro: they're about 2/3 the price of >> the WD RE and they have more cache. > > Hot swap in a drive is normally implemented via pin length, right? > > If so, I can inspect the pins and let you know. > > Greg (resending, apparently I had HTML enabled) I pulled the drives. They appear identical. Definitely the same metal chassis as viewed from the outside. In particular I looked at the length of the SATA connector pins. As expected some were longer than others. But the arrangement was identical on the Barracuda Pro and the Skyhawk. I guess everyone knows that the different lengths are used to control the order of pin connections. The longer pins make contact first on insertion and break contact last on removal. I believe the Skyhawk should be hot-swappable with no problem. That makes sense because the Skyhawk is said to have been engineered to work in a raid array. In part that means the vibration from a drive in the next bay should not have a major impact on the Skyhawk. I expect it to also include hotswap features. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] SSD Only machine - cfq, bfq, deadline?
by John Andersen 14 Dec '16

14 Dec '16

Subject says it all. Would any care to speculate as to which io scheduler one might best use on a machine that had only SSD drive, and no spinning rust? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] leap422 okular printing issue
by Per Jessen 14 Dec '16

14 Dec '16

Printing an A4 page from Okular makes it come out scaled down to what looks like 2/3 size. Printing to the same printserver from 13.1 works fine. I don't even know where to begin to look. Any hints? -- Per Jessen, Zürich (1.0°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

Re: [opensuse] leap422 okular printing issue
by stakanov＠freenet.de 14 Dec '16

14 Dec '16

> -----Ursprüngliche Nachricht----- > Von: Per Jessen > Gesendet: Mi. 14.12.2016 11:49 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] leap422 okular printing issue > > Per Jessen wrote: > >> stakanov(a)freenet.de wrote: >> >>>> -----Ursprüngliche Nachricht Ende----- >>> Sorry if this should be a "thred breaker" but I haven't yet been >>> accepted by another mailer (ip problem it seems). So, to make it >>> short: I am using 42.1 and Lexmark. With 13.1-13.2 no problems. But >>> with 42..1 I had quite a few with scaling. It boils down to the point >>> that with 13.2 and before, the printersettings in the printerfirmware >>> where ingnored or overridden. With 42.1 if there is Legal in the >>> firmware of the printer as size and A4 in the settings of >>> yast.....the thing prints badly formatted. >> >> The only YaST setting I ever use wrt printers is the first one to >> activate network printers, otherwise I never use YaST for anything >> printer-related. Anyway, according to the web-interface on the >> printer, it has A4 in the two input tray, and C5 in the multi-form >> feeder (for envelopes). Normally every print-job could ask for a >> different size and a different media. >> >>> When I did find out and corrected, within the firmware, to A4, the >>> problem stopped. This could also be your case. Look if you do not >>> have B4 or B5 setted for what ever reasons in your printer firmware. >> >> I'm not sure where to look for that. The scaled down output looks >> like it could be A5 size, but it was also shifted about 2cm to the >> right, cutting off those 2cm. >> >>> Or if it is et to "enveloppe". >> >> It looks too small for C5. >> >>> With me that caused disturbances in 42.1 that did NOT manifest before >>> with the very settings. Hope that helps. Controll also the settings >>> in yast. >> >> I'll check. > > There are no page-size related settings in YaST for this printer. It's > all about whether it is the default and which driver to use > (currently 'raw'). > > > > -- > Per Jessen, Zürich (0.6°C) >http://www.hostsuisse.com/ - dedicated server rental in Switzerland. > > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Sorry for being intrusive, in what way you talk to the printer? TCP, IPP, LDP, IPP via CUPS? Raw has sometimes some issue (e.g. if you use a printserver at home you will find that with the AVM Fritzbox you may run into issues with raw, with other servers it may depend on the producer) but mainly due to limitations of the protocol itself. You said you did print the very same(!) document in 13.2 and it worked? Or did you print other documents and they print out well. I trust you did try with another old one (pdf), known to work, to check if this is pdf or raw related? When I had a problem with AVM I changed from IPP to LDP. It was at the time a bit tedious because I had to find out the right setup but worked afterwards. But my Printer was on the usbport of the Fritzbox and the communication via ethernet. I think the most important would be first to check with another PDF, if you haven't done it already of course. If the PDF was created with some special adobe software a vendor lock in is possible. Some of the adobe formats are not working well with OSS (guess why). --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Scary Suse? R me being hax0red?
by cagsm 14 Dec '16

14 Dec '16

Some sudo command give me the funny reply?! What the hecks? Is this serious? Found on a current leap 42.2 > sudo smbstatus -L > root's password: > Listen, burrito brains, I don't have time to listen to this trash. Never seen this message before on a bad password typo? Suse is scaring me :( -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 13

[opensuse] access logs on Nov 30
by jdd 14 Dec '16

14 Dec '16

Hello, Some malicious files where written to my openSUSE (13.1, I know... obsolete :-() on nov 30 How can I trace what access was used, I suspect ftp, but it may also be php thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 14

[opensuse] Remote sound app advice
by Roger Oberholtzer 14 Dec '16

14 Dec '16

I often connect to remote systems via vncviewer (remote is Linux) or rdesktop (remote is Windows). It works great to share the remote desktop with a remote user. One thing I miss is to be able to talk to the remote user at the same time. Obviously, the telephone works. But where is the challenge in doing that? Does anyone have a suggestion for an app supported on openSUSE that allows this? Something that is not too complicated. We don't need conference calls or anything fancy. Just two computers, each with a mic and speakers. If we stay with Linux on both sides, we can add KDE into the mix as that is the desktop on both ends. I see many apps. But they always seem so involved. And some like a server to mediate connections. I would like to avoid that if possible. Just two client apps that talk to each other. Looking forward to suggestions. Preferably ones where the apps are actually used. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 15