For years I use a small server opensuse 11.1. I just need as a mail server (postfix + dovecot + getmail) and to share files. I’ve used it for years without problems. A few months ago I made changes to my network taking any pc with windows 7 and I changed the hardware of my server with opensuse and I ristallato. From there I had continuous problems. In fact, in a completely rhapsodic, the system freezes and I’m forced to restart mechanically. I thought that the problem was the new hardware installed on the server, but it does not. I tried to install other servers with different hardware configurations, but he always stops. Where is the problem? It 'possible that systems with win 7 for whom access to the samba server should send him every now and then in block? Where can I find a log to tell me why it crashes? I would not install a new version of opensuse, I feel very comfortable with this. What advice can you give me? Thank you very much for everything.
On 2013-01-21 13:16, digitaldavid wrote:
> I would not
> install a new version of opensuse, I feel very comfortable with this.
> What advice can you give me? Thank you very much for everything.
openSUSE 11.1 (there is not 11.01) is obsolete and has no maintenance.
You can not use it for a server connected to Internet.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
To expand my previous post: If you’re " comfortable " with a no longer supported OS on a server exposed to the outside world, stick with 11.1, but please note that you’ll be on your own. None of us here still runs 11.1, so we have nothing to compare your situation to, nothing to simulate your issues.
WARNING: since 11.1 is no longer supported, you’ll also miss the security fixes . In the most dramatic case your system will be open for any high school hacker, my guess is that that is the last thing you want.
On 2013-01-21 18:25, Jim Henderson wrote:
>> You can not use it for a server connected to Internet.
> This, however, is not. There’s absolutely no reason someone could not do
> this, but it’s not recommended because of the above statement.
You can, but no sane sysadmin would do it, unless forced. Not
professional, and dangerous.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
On Mon, 21 Jan 2013 21:44:18 +0000, Carlos E. R. wrote:
> On 2013-01-21 18:25, Jim Henderson wrote:
>>> You can not use it for a server connected to Internet.
>> This, however, is not. There’s absolutely no reason someone could not
>> do this, but it’s not recommended because of the above statement.
>
> You can, but no sane sysadmin would do it, unless forced. Not
> professional, and dangerous.
I might disagree. There are people who certainly may do so, and do so
safely, but it requires some extra layers of security.
But what I was clarifying was that your statement made it sound like old
versions self-destruct or something - that is the way I read “you can not
use it for a server connected to [the] Internet.” You can. Whether it’s
well advised or not, well, that’s up for debate and depends highly on a
number of things, including extra measures taken to keep the system
secure.
After all, this isn’t an old version of Windows we’re talking about.
Hi, my “very small” server in not connected to Internet. I use it only to archive my email and to access a public folder from the other pc. That the reason I feel comfortable with my server. The question is: Is it possible that other pc with win 7 (that access to the server via samba) send my server to block? How can I do to understand the reason why it stops. I never had this problem before. Thank you so much.
On Wed, 23 Jan 2013 17:56:01 +0000, digitaldavid wrote:
> Hi, my “very small” server in not connected to Internet. I use it only
> to archive my email and to access a public folder from the other pc.
> That the reason I feel comfortable with my server. The question is: Is
> it possible that other pc with win 7 (that access to the server via
> samba) send my server to block? How can I do to understand the reason
> why it stops. I never had this problem before. Thank you so much.
Not likely the other PC is causing a hard lock. That’s usually
indicative of a hardware issue.
On Wed, 23 Jan 2013 18:52:41 +0000, Jim Henderson wrote:
> Not likely the other PC is causing a hard lock. That’s usually
> indicative of a hardware issue.
Something to look at, incidentally, is overheating - pull the cover open
and clean inside the case really thoroughly - dust it and make sure all
the fans are working properly. Inadequate cooling/airflow can cause a
system to overheat and lock up.
Also make sure the airways in the power supply are clear and that fan is
working. Otherwise, the PS could overheat, causing it to less
effectively regulate power, and inconsistent power from the PS could
cause voltage problems and damage to the system board.
On 1/21/2013 6:16 AM, digitaldavid wrote:
>
> Hello to all.
>
<snip>
> Where is the problem? It 'possible that systems with win 7 for
> whom access to the samba server should send him every now and then in
> block? Where can I find a log to tell me why it crashes? I would not
> install a new version of opensuse, I feel very comfortable with this.
> What advice can you give me? Thank you very much for everything.
>
>
digitaldavid;
Check the system log (/var/log/messages) and the samba logs
(/var/log/samba/log.[s,n]mbd ). You can make the Samba logs more verbose by
adding to the [global] section of/etc/samba/smb.conf the parameter:
log level = 3
For what its worth, I doubt that Windows 7 (or any other client) is creating the
crash.
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
I thought that the problem could be something such as temperature or dust, but I changed 3 different pc with different cpu and motherboard and I have the same problem sametimes it stops. I’ll check the logs and tell you something. Thank you again.
On 01/24/2013 11:06 AM, digitaldavid wrote:
> I changed 3 different pc with different cpu and motherboard
> and I have the same problem sametimes it stops.
i now assume you are using the same openSUSE 11.1 install media on all
three of these different machines as well as your “small server”…
since 11.1 is no longer supported, as you install on any machine you do
not have the ability to update the software on that media to its state
when 11.1 went past its end of life in July 2010…
which means the software you are installing was FROZEN in time somewhere
around early December 2008 (over FOUR years ago)…
and, let me guess maybe there is one or more finger print or scratch
on the install media–so i wonder have you lately run the disk’s
self-test to see if you still have good media?
to do that boot to the first green screen and select “Check Installation
Media” as you see here http://tinyurl.com/3qde66h
if the self-test shows any errors do NOT use it to install…
next: it is very possible that any or all of the machines available to
you today includes hardware that did not exist in 2008, and therefore
openSUSE 11.1 will never work correctly on them, ever…
recommend you move to a supported version–no matter how “comfortable”
you feel about your small servers security, it still is just OLD
software on new hardware…
and, until you do move to asupported version i will consider this thread
as just a way to tie up potential volunteer helpers in the lost cause of
trying to get unsupported software on dubious install media working.
so, this is my only post in this thread… good luck.
I don’t thik that the problem is supported or unsopported version, becouse I’m sure that it works before for same years and now (without any change) it doesn’t. That the reason why I decide to write this thread.
And the problem still remain.
Infact I Check Installation Media and it’s ok. Even the log files are ok, and I can’t understand why it goes in crash. And the hardware is not so new, and it works before with the same OS.
So I thought that this can be an intersting stuff for You and that You can help me to solve this problem.
