Hello All,
My apologies for the late reply. Been super busy with other work.
I haven't been able to run the memory test yet. However, no segfaults have
occurred since moving the director VM to a different ESXi host. So, it's
obviously something with the host machine. The only odd thing is no
On 01/27/2017 10:29 PM, Craig Shiroma wrote:
The VM that bacula-dir is running on is configured exactly the same.
In these discussions, I don't think Ive seen you mention checking SMART
info.
--
Check out the vibrant
Hi Josh,
>Are the VM's configured exactly the same on both ESXi hosts? A difference
in VCPU, memory limit, etc. in the VM config could potentially reveal the
problem.
The VM that bacula-dir is running on is configured exactly the same. No
changes were made to it before I vMotioned it to a differ
On 1/27/2017 4:04 AM, Craig Shiroma wrote:
Hi All,
Thank you very much for all the help!
Sorry for the delayed reply. What I've done so far is move the
Director VM to a different ESXi host. So far, no segfaults although
I'll give it a week before raising the all clear flag.
Are the VM'
Hi All,
Thank you very much for all the help!
Sorry for the delayed reply. What I've done so far is move the Director VM
to a different ESXi host. So far, no segfaults although I'll give it a
week before raising the all clear flag.
There are normally many VMs on the ESXi host that the Director
On 2017-01-25 07:19, Josh Fisher wrote:
> If you compiled from source, then check your compiler flags
If it ran fine before, that's not impossible, but rather unlikely to be
the cause. You'd expect at least a major libc update or something to
break it...
One thing I forgot to mention is just r
On 1/24/2017 1:57 PM, Craig Shiroma wrote:
This is what appears in /var/log/messages:
Jan 23 22:42:39 bup05 bacula-dir: Bacula interrupted by signal 11:
Segmentation violation
If you compiled from source, then check your compiler flags or try a RPM
package. Otherwise, it is likely a hardwar
On Tuesday 2017-01-24 09:48:25 Craig Shiroma wrote:
> Thanks, Dimitri!
>
> I checked the hardware server logs (not /var/log/messages) and don't see
> any memory alerts.
Have you tried to put server offline and run the memtest86+ out of the
system (from a bootable CD or USB stick) for 12+ hours?
Thanks, Dimitri!
I checked the hardware server logs (not /var/log/messages) and don't see
any memory alerts.
-craig
On Tue, Jan 24, 2017 at 9:09 AM, Dimitri Maziuk
wrote:
> On 01/24/2017 12:57 PM, Craig Shiroma wrote:
> > This is what appears in /var/log/messages:
> >
> > Jan 23 22:42:39 bup05
On 01/24/2017 12:57 PM, Craig Shiroma wrote:
> This is what appears in /var/log/messages:
>
> Jan 23 22:42:39 bup05 bacula-dir: Bacula interrupted by signal 11:
> Segmentation violation
Try googling for sig11?
You may have a DIMM or some other hardware going bad.
--
Dimitri Maziuk
Programmer/s
This is what appears in /var/log/messages:
Jan 23 22:42:39 bup05 bacula-dir: Bacula interrupted by signal 11:
Segmentation violation
On Tue, Jan 24, 2017 at 8:44 AM, Craig Shiroma
wrote:
> Hello All,
>
> Within the last 3-4 weeks, our Bacula 7.0.5 on RHEL 6 has experienced
> bacula-dir segfaul
Hello All,
Within the last 3-4 weeks, our Bacula 7.0.5 on RHEL 6 has experienced
bacula-dir segfaults once or twice a week. Before that everything ran fine.
Memory and CPU look fine on our Director server. Nothing has changed on
the server before the segfaults started happening as far as I can
12 matches
Mail list logo
